这里我声明了一个变量，然后我把那个幻灯片上的公式，用键盘上的字符翻译成了，浮点数值。
C So here I'm declaring a variable called c, and I'm pretty much translating the formula from the slide using the characters on my keyboard to a floating point value.
但它在检测是否有无意中翻译掉的字符串方面也有用。
But it also is helpful in detecting that there are not any inadvertent translations.
使用这些函数处理已翻译字符串会导致意外结果，比如在UI中显示怪异的翻译，或造成函数失败。
Processing translated character strings by these functions can cause unexpected results, such as bad translation words showing on the UI or functions failing.
由于语言和文化的差异，在某个字符串中的动词翻译成其他语言时不再是动词。
The verb used in this string might not be used in another string due to differences in language or culture.
记住翻译人员将只能看到字符串——而不是运行的应用程序。
Keep in mind that translators will only see the strings — not the running application.
从应用程序中提取将放入到属性文件的所有可翻译字符串，并将它们放入到各自的文件夹中。
Extract all the translatable strings from the applications to be placed in properties files and put them into their respective folders.
提示：在翻译之前，要记得在词汇表数据库中运行检索功能，以减少未翻译的字符串的数量。
Tip: Before translation, remember to run the retrieve function in the glossary database to reduce the number of untranslated strings.
有时候，很难判断一个字符串是否是可翻译的。
支持表情字符：将：-这样的字符组合翻译成适当的笑脸图像。
Allow emoticons: Translate character groupings such as: - into the appropriate image of a smiley face.
翻译器需要打开词汇表数据库，复制英文字符串，翻译字符串，然后将用新语言表达的字符串存储到词汇表数据库。
Translators need to open the glossary database, copy an English string, translate it, and store the strings in the new language to the glossary database.
只需在词汇表中创建新的或更改过的字符串，从而减少翻译工作和成本。
Only the new or changed strings are created in the glossary, thus saving translation effort and cost.
简而言之，如果仅通过连接字符串来合并翻译后的文本，那么合并出来的句子可能不符合目标语言的语法。
In short, if the translated text is constructed just by concatenating the strings, the constructed sentences might no longer be grammatically correct in other languages.
示例中仅包含这些字符串的英文版本，但是您可以将这些字符串翻译为法文然后放到 fr-FR文件夹中，或者翻译为德文放到 de-DE 文件夹中，等等。
The example only has a US English version of these strings, but you could translate them to French and place them within a fr-FR folder, to German and use a de-DE folder, and so on.
至此，已经有了一个标记数据库和一个包含英文字符串和翻译后的字符串的词汇表。
Now, you have a tag database and a glossary that contains the English strings and the translated strings.
第二个阶段(“翻译准备”)包括把字符串转化成专门的xml词汇表，以及重用已有的翻译。
The second stage (" translation preparation ") consists of converting strings into a special XML vocabulary and reusing existing translations if they are available.
L10N团队将使用翻译数据库来翻译新字符串并且重新翻译更改的字符串。
The L10N team uses the translation database to translate new strings and retranslate changed strings.
在清单11中，在脚本的开头就定义了所有可翻译和不可翻译的字符串，这增强了脚本的可读性。
In Listing 11, all the translatable and non-translatable strings have been defined at the beginning of the script, which makes the script easy to read.
标记这些字符串可以防止它们被翻译，并防止全球化后出现潜在的缺陷。
Marking these stings prevents them from being translated and prevents potential defects after globalization.
为了避免混淆，需要仔细检查字符串，确保可翻译属性文件中没有dnt字符串，而且DNT文件中也没有可翻译字符串。
To prevent confusion, you need to review the strings carefully to make sure that no DNT strings are in translatable properties files and no translatable strings are in DNT files.
很明显，在对用作编程条件的字符串进行翻译时，会带来功能性问题。
Obviously functional issues can occur if these strings that have been used as programming conditions are translated.
在新的过程中，dnt字符串保存在单独的文件中，而没有与可翻译字符串混在一起。
In the new process, DNT strings are kept in separate files and do not mix with translatable strings.
首先，您需要收集将显示在用户界面页中的所有可翻译字符串，如门户网页、电子邮件等等。
First, you need to collect all the translatable strings that will be shown in user interface pages, such as portal Web pages, E-mail, and so on.
清单5的例子将可翻译字符串作为编程条件。
Listing 5 shows an example that USES translatable strings as programming conditions.
翻译者可以在英文(基本语言)字符串上附加不同语言的翻译。
Translators can append the translation for different languages on the English (base language) strings.
记住，永远不要将可翻译字符串用作编程条件。
You should never use translatable strings as programming conditions.
您还使用经过翻译的字符串，让新闻组件国际化。
You also used traanslated strings to internationalize your news component.
而在属性文件中，可翻译字符串和不可翻译字符串分放在不同的文件中。
In the properties files, translatable strings and untranslatable strings are separated into different files.
词汇表数据库中有很多英文字符串需要被翻译，如图6所示。
There are a lot of English strings in the glossary database to be translated as shown in figure 6.
在图5中列出的所有字符串中，对话框顶部的空白字符串不需要翻译。
Of all the strings listed in Figure 5, the blank string at the top of the dialog doesn't need to be translated.
在属性文件中，仅提取可翻译的字符串。
In properties files, only the latter translatable strings are resourced out for translation.
应用推荐