简体中文Solaris系统管理员资料 (Multilingual BigAdmin)

 

欢迎大家到简体中文版的 BigAdmin System Administration Portal - http://www.sun.com/bigadmin/hubs/multilingual/simp_chinese/

简体中文版的BigAdmin的目标是为世界各地的中文Solaris系统管理员提供服务。您不但可以阅读许多中文版BigAdmin文章,还可以上载您自己的文章、内容和各种相关知识并参与网站的合作建设。

我们将从翻译部分英文版BigAdmin的文章开始。欢迎您经常光临我们的网站，通过反馈标签对我们的翻译质量提供建议，把您希望翻译的BigAdmin的话题或内容或者需要对其他语种的支持告诉我们，您宝贵的意见对我们非常重要。

我们最大的愿望是与您和社区一起合作，在全球创建和扩充BigAdmin的内容。

“用我们最了解的语言来共享知识！”

Posted at 07:00PM Jul 24, 2007 by byuan in Globalization  |  Comments[0]

Best practices of handling apostrophes ( ’) in .properties files

Problem: java.text.MessageFormat requires single ( ’) be escaped using double  ( ’’), other classes
don't have this requirement.

 

Best practices:

• Double the apostrophe (’’) when you see bracket(s) ({}) in the same message.
• Do not double the apostrophe( ’) if there is no bracket ({}) in the same message.
• Do not double the apostrophe( ’) if you see an apostrophe in the original English contents since it should have been confirmed to be displayed properly.
• Do not use apostrophe( ’), use quotation mark (′) instead.

Posted at 09:23AM May 29, 2007 by byuan in Globalization  |  Comments[4]

Automation in G11n end to end process

What can be or should be automated in G11n end to end process? Here are some candidates:

1. File verification, both English source files and translated files can be verified or validated using some tools.

2. Leverage from previous translations, this can be done in software
workspace, using a message database or even a translation memory.

3. Translation process management or workflow, a tool to streamline, simplify or standardize the translation process.

4. Testing environment setup like machine reservation, OS installation, application installation, etc.

5. Test suites execution.

6. Reports or metrics generation.

7. Release engineering: workspace synchronization, package, patch generation and integration, product image download, etc.

...

Posted at 08:33AM Nov 02, 2006 by byuan in Globalization  |  Comments[0]

RFC 4646 and RFC 4647 about Language tags and matching in Web applications

RFC 4646, in combination with RFC 4647, is to replace RFC 3066, which replaced RFC 1766.


Tags for Identifying Languages 
Matching of Language Tags

Posted at 09:15AM Nov 01, 2006 by byuan in Globalization  |  Comments[0]

How to do i18n testing

Just want to share two great articles posted to i18n-prog@yahoogroups.com
from Addison Phillips who is the Globalization Architect in Yahoo! Inc.


International Testing Basics  

Learn To Type Japanese and Other Languages

Posted at 08:59AM Nov 01, 2006 by byuan in Globalization  |  Comments[2]

Measurement and best practices of i18n and l10n testing (2)

To better measure the i18n and l10n testing efficiency or the i18n and
l10n quality, it's very critical to do the following things:

1. To use standard keywords for different kind of bugs, the keywords
should be in a easy to understand and remember convention, such as
i18n-external, i18n-internal, l10n-external, l10n-internal,
g11n-external, g11n-internal, there shouldn't have too many keywords
like language specific or team specific unless it's really necessary.

2. Don't use i18n/l10n specific subcategories unless it's really
necessary, especially the i18n subcategory since i18n problems should
be part of the core problems, not problems of an additional feature.

3. To follow standard definitions of the bug priority and severity, so that the nubmers of P1, P2 or P3 bugs do make sense.

4. To generate metrics frequently (automatically) to compare progress
or trends among products, releases, teams, etc. Then to leverage best
practices from those who do the best or find the root causes and
develop an improvement plan for those who do the worst.

Posted at 02:28PM Oct 30, 2006 by byuan in Globalization  |  Comments[0]

Make or buy g11n automation tools?

In order to improve efficiency, we need to use more and more automation
in the g11n end to end process, from translation workflow and
translation memory management to localization engineering, from release
engineering to localization testing, from project management to
business operation, etc.



Should we implement those automation tools internally or buy commercial
products? There sure have pros and cons in both solutions, but the
following are some pros of commercial products in the context of a
market system which rely on specialization (Campbell R. McConnell and
Stanley L. Brue, 2005, "Economics"):



The majority of consumers produce virtually none of the goods and
services they consume, and they consume little or nothing of  what
they produce. The worker who devotes 8 hours a day to installing
windows in Fords may own a Honda. Many farmers sell their milk to the
local dairy and then buy margarine at the local grocery store. Society
learned long ago that self-sufficiency breeds inefficiency.



Human specialization - called the division of labor - contributes to a society's output in several ways:

• Specialization makes use of differences in ability.
  Sepcialization enables individuals to take advantage of existing
  differences in their abilities and skills. If A is strong and swift and
  good at tracking animals, and B is weak and slow but patient, their
  distribution of talents can be most efficiently used if A hunts and B
  fishes.
  
  


• Specialization fosters learning by doing. Even if the abilities
  of A and B are identical, specialization may still be advantageous. By
  devoting all your time to a single task, you are more likely to develop
  the skills it requires and to devise improved techniques than you would
  by working at a number of different tasks. You learn to be a good
  hunter by going hunting every day.
  
  


• Specialization saves time. By devoting all your time to a single
  task, you avoid the loss of time incurred in shifting from one job to
  another.
  
  

So if someone is already providing a great tool with a reasonable
price, should we implement another similar or worse tool with limited
internal resources?



But buying commercial products might demotivate internal people who are
very interested in the same technology or tools, then it would be very
important to talk to those people to understand their wants, to
motivate them according to Herzgerg's two factor theory which I 
explained in the "Motivation issue in G11n group"

Posted at 09:10PM Oct 29, 2006 by byuan in Globalization  |  Comments[0]

I18n and non I18n bug submission and resolving trends comparison

The following graphic shows the different trends of the i18n and non
i18n bug submission and resolving trends in one small product.

One problem is both i18n and non i18n bugs were filed starting from day
10, bug non i18n bugs were getting resolved starting from day 100,
while i18n bugs were getting resolved starting from day 200, ideally a
product team should resolve i18n bugs  earlier and more quickly so
that l10n can be started early and released at the same time with base
products.

The second problem is i18n bugs were found continuously till the end of
the release even when l10n testing should have already started or
finished, it means a lot of i18n bugs were found during l10n testing
and thus  translation  and l10n engineering/testing will all
have to be reworked many times which means extra time and
resources/cost will occur.

Posted at 02:19PM Oct 28, 2006 by byuan in Globalization  |  Comments[2]

Measurement and best practices of i18n and l10n testing (1)

To measure how well you are doing i18n and l10n testing, here are some of the metrics:



1. How many i18n bugs are found before and after l10n testing is
started. Ideally most of the i18n bugs should be found and resolved at
the same time with the other functional bugs, and very few i18n bugs
will be found when l10n testing is started. The later i18n bugs are
found, the more l10n rework might happen, and the less time to resolve
those i18n bugs and thus the worse the g11n quality the product will be.



2. How soon can i18n bugs or l10n bugs be resolved compared with non
i18n and l10n bugs. I18n and l10n bugs shouldn't take longer time to be
fixed than the other bugs.



3.  How many i18n test cases or suites are reused for l10n
testing? The best practice is to reuse all i18n test cases and suites
in l10n testing, the difference between i18n and l10n testing is the
messages will be pseudo l10n messages during i18n testing but will be
real translations in l10n testing.



4. What percent of i18n testing and l10n testing is automated, the more
automation in i18n testing, the more configurations/platforms can be
covered. The more automation in l10n testing, the more time can be
spent on manual checking of the translations in the context.



5. How much leverage among different languages, builds and platforms
during i18n testing and l10n testing, the best practice is define a
complete matrix to rotate among languages and platforms for different
builds.

Posted at 12:43PM Oct 26, 2006 by byuan in Globalization  |  Comments[0]

How to dynamically change the display language of a web application based on user preference.

See the i18n sample codes of Java EE  at http://java.sun.com/javaee/reference/code/

Posted at 09:31PM Oct 25, 2006 by byuan in Globalization  |  Comments[0]

Want to learn more about Solaris i18n?

Two suggestions for how to learn more about Solaris i18n:

1. Read the Solaris International Language Environments Guide

2. Join the OpenSolaris i18n and l10n community , its discussion
alias is i18n-discuss@opensolaris.org

Posted at 09:50AM Oct 24, 2006 by byuan in Globalization  |  Comments[0]

How to do i18n to help l10n?

Better and earlier i18n implementation and testing can help l10n in the following ways:

1. To reduce translation cost: If engineers can use proper English
messages, reuse previous messages, use common messages across
components or products, or don't modify messages frequently, then the
translation team would be able to leverage previous translations
easily, or even can do machine translation while not reducing the
quality of translations.

2. To improve translation quality: If engineers can use consistent
terms among UI, error messages, online help and even help technical
writers in the documentation, and provide detailed explanation of new
terminologies, then translation vendors or l10n engineers will be able
to better translate all contents properly and consistently.

3. To reduce l10n testing efforts and cost: If engineering team have
clear  i18n design documentation,i18n test plan, test cases, test
results or reports before translation and l10n is started, then l10n
team would be able to leverage most of them and do efficient and
effective l10n testing. Early i18n testing can avoid duplcated common
i18n problems found during l10n testing in many languages.

4. To improve the l10n quality: Early i18n testing can make sure all
critical i18n problems are resolved, the i18n problems found during
l10n testing may not be fixed before GA because usually it's too late
in a release.

Posted at 10:26PM Oct 23, 2006 by byuan in Globalization  |  Comments[0]

A great i18n check list

A great i18n check list posted on Sun's globalization website:



http://developers.sun.com/dev/gadc/i18ntesting/checklists/allquestions/allquestions.html

Posted at 10:16AM Oct 23, 2006 by byuan in Globalization  |  Comments[0]

i18n in web services

If you'd like to know more about i18n in web services, I'd suggest you
start from the great page on w3.org:

http:///www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730

I know it's very huge but you can start from the section of "What are i18n and l10n?" - http:///www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730/#IDARXSO

After that, goto some other sections that are related to your projects.

Posted at 07:15PM Oct 21, 2006 by byuan in Globalization  |  Comments[0]

I18n/L10n test guide line

Here are some guide lines or strategies for globalization testing,
sorry but you have to scroll down to see the table for unknow reasons:

Category	I18n functional testing	Pseudo l10n testing	L10n message testing	L10n functional testing
What to test	Installation and uninstallation of l10n support in CLI/GUI/Silent modes, all functions especially input, output (fonts, display and printing) and internal conversion or processing of non ASCII characters in non English environment.	Hardcoded messages hardcoded button/menu/label width, garbages, white boxes, question marks, mismatched encodings or bad layouts in CLI/GUI installation, CLI commands, BUI, Error messages, OLH, etc.	Correct and consistent translations of all of the messages.	All of the Locale data, all of the input methods, the fonts, display, and printing in all applications, all of the converters, etc.
Who to write test cases	I18n developers, base team or i18n SQEs (Software Quality Engineers)	I18n developers, base SQEs	I18n developers, base SQEs	L10n developers, l10n SQEs
Who to do the testing	I18n developers, base team or i18n SQAs (Software Quality Asurances)	I18n developers, base SQEs, l10n SQEs, l10n Ces, l10n tech leads, etc	L10n SQAs	10n developers, l10n SQAs
Where to test	In one Asian multiple byte locale of each OS release on all platforms	In one locale of one OS release On all platforms	One language in one release on one platform	all releases on all platforms
When to test	When the features are implemented or bugs are fixed, before l10n message engineering is started	During development, while messages are being translated, before l10n testing is started	After the message translations are integrated	When the features are implemented or bugs are fixed
How often to test	Whenever there are new features or bug fixes	Whenever there are message updates	Rotate sub test groups among builds	Whenever there are new features or bug fixes

Posted at 01:40PM Oct 19, 2006 by byuan in Globalization  |  Comments[0]