Bug 973563 - Questioning word, Asynchronous updates, and a typo
Summary: Questioning word, Asynchronous updates, and a typo
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation - Translation
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: jito
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-12 08:33 UTC by Osamu Nagano
Modified: 2014-02-12 22:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build: CSProcessor Builder Version 1.10 Build Name: 6895, Installation Guide-6.1-1 Build Date: 12-06-2013 05:00:14 Topic ID: 34290-450654 [Specified]
Last Closed: 2014-02-12 22:46:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Osamu Nagano 2013-06-12 08:33:39 UTC 
Title: 3.7.1 パッチングの仕組み

Describe the issue:
1. "Asynchronous updates (非同期更新)" sounds like a technical term of programming.
--
非同期更新: 既存製品の通常のアップグレードサイクル以外にリリースされる 1 回限りのパッチです。
--

2. A typo, dropping "S" for SELinux.
--
欠陥の影響を低減する他の要素はあるか (ファイアウォール、ecurity-Enhanced Linux、コンパイラー指示文など)。
--

Suggestions for improvement:
1. "Occasional updates (随時の更新)" or something like that.
2. "... Security-Enhanced Linux ..."

Additional information:
Comment 1 Osamu Nagano 2013-06-12 08:35:55 UTC 
One more on the same line of 2.

3. "compiler directives (コンパイラー指示文)"
"コンパイラーディレクティブ" is more natural.
Comment 2 sgilda 2013-06-19 19:23:37 UTC 
I checked the Installation Guide here and don't see a missing "S" in "Security-Enhanced Linux": https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html-single/Installation_Guide/index.html

Are you referring to the translated version?
Comment 3 Osamu Nagano 2013-06-20 00:29:02 UTC 
Yes.
I've been asked to review the Japanese translation and it's here:

http://docbuilder.usersys.redhat.com/ja/6895/#About_Patching_Mechanisms
Note You need to log in before you can comment on or make changes to this bug.