blocks|key|233683|text|NSLocalizedString有一些限制，但它是Cocoa的核心，所以编写自定义代码来处理本地化是不合理的，这意味着您将不得不使用它。也就是说，一个小工具可以有所帮助，下面是我如何进行的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|233684|更新字符串文件|233685|genstrings会覆盖您的字符串文件，丢弃您之前的所有翻译。我编写了update_strings.py来解析旧的字符串文件，运行genstrings并填充空白，这样您就不必手动恢复现有的翻译。该脚本尝试尽可能接近地匹配现有的字符串文件，以避免在更新它们时有太大的差异。|233686|为字符串命名|233687|如果您按照通告的方式使用NSLocalizedString：|233688|NSLocalizedString(@"Cancel+or+continue?",+@"Cancel+notice+message+when+a+download+takes+too+long+to+proceed");|code-block|syntax|javascript|233689|您可能最终会在代码的另一部分中定义相同的字符串，这可能会发生冲突，因为相同的英语术语在不同的上下文中可能具有不同的含义(脑海中会想到OK和Cancel+)。这就是为什么我总是使用无意义的全大写字符串和特定于模块的前缀，以及非常精确的描述：|233690|NSLocalizedString(@"DOWNLOAD_CANCEL_OR_CONTINUE",+@"Cancel+notice+window+title+when+a+download+takes+too+long+to+proceed");|233691|在不同位置使用相同的字符串|233692|如果多次使用相同的字符串，则可以像以前一样使用宏，或者将其作为实例变量缓存在视图控制器或数据源中。这样，你就不必重复描述，因为它可能会变得陈旧，并且在相同本地化的实例之间变得不一致，这总是令人困惑。由于实例变量是符号，您将能够对这些最常见的转换使用自动完成，并对特定的转换使用“手动”字符串，这只会出现一次。|233693|我希望通过这些技巧，您将更高效地使用Cocoa本地化！|233694|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ndfred/xcode-tools/blob/master/update_strings.py^0|0|H|0|0|0|A|1U|A|10|H|0|0|0|C|H|0|0|1U|2|1X|6|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1D|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|J|3|K|5|6|7|1M|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|N|3|O|5|P|7|1Q|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]]|D|@]|E|$]]|$1|U|3|V|5|P|7|1W|8|@]|D|@]|E|$Q|R]]|$1|W|3|X|5|6|7|1X|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|12|3|-4|5|6|7|20|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]]]

<code>NSLocalizedString</code> has a few limitations, but it is so central to Cocoa that it's unreasonable to write custom code to handle localization, meaning you will have to use it. That said, a little tooling can help, here is how I proceed:

<h2>Updating the strings file</h2>

<code>genstrings</code> overwrites your string files, discarding all your previous translations.
I wrote <a href="https://github.com/ndfred/xcode-tools/blob/master/update_strings.py" rel="noreferrer">update_strings.py</a> to parse the old strings file, run <code>genstrings</code> and fill in the blanks so that you don't have to manually restore your existing translations.
The script tries to match the existing string files as closely as possible to avoid having too big a diff when updating them.

<h2>Naming your strings</h2>

If you use <code>NSLocalizedString</code> as advertised:

<pre><code>NSLocalizedString(@"Cancel or continue?", @"Cancel notice message when a download takes too long to proceed");
</code></pre>

You may end up defining the same string in another part of your code, which may conflict as the same english term may have different meaning in different contexts (<code>OK</code> and <code>Cancel</code> come to mind).
That is why I always use a meaningless all-caps string with a module-specific prefix, and a very precise description:

<pre><code>NSLocalizedString(@"DOWNLOAD_CANCEL_OR_CONTINUE", @"Cancel notice window title when a download takes too long to proceed");
</code></pre>

<h2>Using the same string in different places</h2>

If you use the same string multiple times, you can either use a macro as you did, or cache it as an instance variable in your view controller or your data source.
This way you won't have to repeat the description which may get stale and get inconsistent among instances of the same localization, which is always confusing.
As instance variables are symbols, you will be able to use auto-completion on these most common translations, and use "manual" strings for the specific ones, which would only occur once anyway.

I hope you'll be more productive with Cocoa localization with these tips!

blocks|key|2895695|text|同意ndfred，但我想补充一下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2895696|第二个参数可以用作...默认值！！|2895697|(NSLocalizedStringWithDefaultValue不能正常使用genstring，这就是我提出这个解决方案的原因)|2895698|下面是我使用NSLocalizedString自定义实现，它使用注释作为默认值：|2895699|1。在预编译头文件(.pch文件)中，重新定义'NSLocalizedString‘宏：|offset|length|style|BOLD|2895700|//+cutom+NSLocalizedString+that+use+macro+comment+as+default+value
#import+"LocalizationHandlerUtil.h"

#undef+NSLocalizedString
#define+NSLocalizedString(key,_comment)+[[LocalizationHandlerUtil+singleton]+localizedString:key++comment:_comment]|code-block|syntax|javascript|2895701|2.创建实现本地化处理程序的类|2895702|#import+"LocalizationHandlerUtil.h"

@implementation+LocalizationHandlerUtil

static+LocalizationHandlerUtil+*+singleton+=+nil;

%2B+(LocalizationHandlerUtil+*)singleton
{
++++return+singleton;
}

__attribute__((constructor))
static+void+staticInit_singleton()
{
++++singleton+=+[[LocalizationHandlerUtil+alloc]+init];
}

-+(NSString+*)localizedString:(NSString+*)key+comment:(NSString+*)comment
{
++++//+default+localized+string+loading
++++NSString+*+localizedString+=+[[NSBundle+mainBundle]+localizedStringForKey:key+value:key+table:nil];

++++//+if+(value+==+key)+and+comment+is+not+nil+->+returns+comment
++++if([localizedString+isEqualToString:key]+&&+comment+!=nil)
++++++++return+comment;

++++return+localizedString;
}

@end|2895703|3.使用它！|2895704|确保在应用程序构建阶段添加运行脚本，以便在每次构建时更新Localizable.strings文件，即在Localized.strings文件中添加新的本地化字符串：|2895705|我的构建阶段脚本是一个shell脚本：|2895706|Shell:+/bin/sh
Shell+script+content:+find+.+-name+\*.m+%7C+xargs+genstrings+-o+MyClassesFolder|2895707|因此，当您在代码中添加以下新行时：|2895708|self.title+=+NSLocalizedString(@"view_settings_title",+@"Settings");|2895709|然后执行构建，您的./Localizable.scripts文件将包含以下新行：|2895710|/*+Settings+*/
"view_settings_title"+=+"view_settings_title";|2895711|由于'view_settings_title‘的键值为==，所以自定义LocalizedStringHandler将返回注释，即‘设置’|2895712|瞧啊:-)|2895713|entityMap^0|0|0|0|0|0|18|0|0|0|D|0|0|0|6|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1L|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1M|8|@$J|1N|K|1O|L|M]]|9|@]|A|$]]|$1|N|3|O|5|P|7|1P|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1Q|8|@$J|1R|K|1S|L|M]]|9|@]|A|$]]|$1|U|3|V|5|P|7|1T|8|@]|9|@]|A|$Q|R]]|$1|W|3|X|5|6|7|1U|8|@$J|1V|K|1W|L|M]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1X|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|12|3|13|5|P|7|1Z|8|@]|9|@]|A|$Q|R]]|$1|14|3|15|5|6|7|20|8|@]|9|@]|A|$]]|$1|16|3|17|5|P|7|21|8|@]|9|@]|A|$Q|R]]|$1|18|3|19|5|6|7|22|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|P|7|23|8|@]|9|@]|A|$Q|R]]|$1|1C|3|1D|5|6|7|24|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|25|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|26|8|@]|9|@]|A|$]]]|1H|$]]

Agree with ndfred, but I would like to add this:

Second parameter can be use as ... default value!!

(NSLocalizedStringWithDefaultValue does not work properly with genstring, that's why I proposed this solution)

Here is my Custom implementation that use NSLocalizedString that use comment as default value:

1 . In your pre compiled header (.pch file) , redefine the 'NSLocalizedString' macro:

<pre><code>// cutom NSLocalizedString that use macro comment as default value
#import "LocalizationHandlerUtil.h"

#undef NSLocalizedString
#define NSLocalizedString(key,_comment) [[LocalizationHandlerUtil singleton] localizedString:key comment:_comment]
</code></pre>

2. create a class to implement the localization handler

<pre><code>#import "LocalizationHandlerUtil.h"

@implementation LocalizationHandlerUtil

static LocalizationHandlerUtil * singleton = nil;

+ (LocalizationHandlerUtil *)singleton
{
 return singleton;
}

__attribute__((constructor))
static void staticInit_singleton()
{
 singleton = [[LocalizationHandlerUtil alloc] init];
}

- (NSString *)localizedString:(NSString *)key comment:(NSString *)comment
{
 // default localized string loading
 NSString * localizedString = [[NSBundle mainBundle] localizedStringForKey:key value:key table:nil];

 // if (value == key) and comment is not nil -&gt; returns comment
 if([localizedString isEqualToString:key] &amp;&amp; comment !=nil)
 return comment;

 return localizedString;
}

@end
</code></pre>

3. Use it!

Make sure you add a Run script in your App Build Phases so you Localizable.strings file will be updated at each build, i.e., new localized string will be added in your Localized.strings file:

My build phase Script is a shell script:

<pre><code>Shell: /bin/sh
Shell script content: find . -name \*.m | xargs genstrings -o MyClassesFolder
</code></pre>

So when you add this new line in your code:

<pre><code>self.title = NSLocalizedString(@"view_settings_title", @"Settings");
</code></pre>

Then perform a build, your ./Localizable.scripts file will contain this new line:

<pre><code>/* Settings */
"view_settings_title" = "view_settings_title";
</code></pre>

And since key == value for 'view_settings_title', the custom LocalizedStringHandler will returns the comment, i.e. 'Settings"

Voilà :-)

blocks|key|234625|text|#define+PBLocalizedString(key,+val)+\

[[NSBundle+mainBundle]+localizedStringForKey:(key)+value:(val)+table:nil]|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|234626|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>#define PBLocalizedString(key, val) \

[[NSBundle mainBundle] localizedStringForKey:(key) value:(val) table:nil]
</code></pre>

blocks|key|233722|text|至于Xcode中字符串的自动补全，您可以尝试使用https://github.com/questbeat/Lin。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|233723|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/questbeat/Lin^0|O|W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

As for autocompletition for strings in Xcode, you could try <a href="https://github.com/questbeat/Lin" rel="nofollow noreferrer">https://github.com/questbeat/Lin</a>.

blocks|key|230808|text|我写了一个脚本来帮助维护多语言的Localizable.strings。虽然它在自动完成方面没有帮助，但它有助于使用命令合并.strings文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230809|merge_strings.rb+ja.lproj/Localizable.strings+en.lproj/Localizable.strings|code-block|syntax|javascript|230810|有关更多信息，请参阅：https://github.com/hiroshi/merge_strings|offset|length|230811|我希望你们中的一些人会发现它很有用。|230812|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/hiroshi/merge_strings^0|0|0|B|14|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@$I|X|J|Y|1|Z]]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I wrote a script to help maintaining Localizable.strings in multiple languages. While it doesn't help in autocompletion it helps to merge .strings files using command:

<pre><code>merge_strings.rb ja.lproj/Localizable.strings en.lproj/Localizable.strings
</code></pre>

For more info see:
<a href="https://github.com/hiroshi/merge_strings" rel="nofollow">https://github.com/hiroshi/merge_strings</a>

Some of you find it useful I hope.

blocks|key|2895808|text|在iOS+7和Xcode5中，你应该避免使用'Localization.strings‘方法，而使用新的’基本本地化‘方法。如果你在谷歌上搜索“基础本地化”，周围有一些教程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2895809|苹果文档：Base+localization|offset|length|2895810|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/prerelease/ios/documentation/MacOSX/Conceptual/BPInternational/InternationalizingYourUserInterface/InternationalizingYourUserInterface.html^0|0|5|H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

with iOS 7 &amp; Xcode 5, you should avoid using the 'Localization.strings' method, and use the new 'base localisation' method. There are some tutorials around if you google for 'base localization'

Apple doc : <a href="https://developer.apple.com/library/prerelease/ios/documentation/MacOSX/Conceptual/BPInternational/InternationalizingYourUserInterface/InternationalizingYourUserInterface.html" rel="nofollow">Base localization</a>

blocks|key|230854|text|就我自己而言，我经常忙于编码，忘记将条目放入.strings文件中。因此，我有帮助器脚本来查找我需要放回.strings文件中并进行翻译的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230855|当我在NSLocalizedString上使用我自己的宏时，请在使用之前检查并更新脚本，因为为了简单起见，我假设nil用作NSLocalizedString的第二个参数。您想要更改的部分是|offset|length|style|BOLD|230856|NSLocalizedString$@(".*?")\s*,\s*nil$+|code-block|syntax|javascript|230857|只需将其替换为与您的宏和NSLocalizedString使用相匹配的内容即可。|230858|脚本来了，你只需要第三部分。剩下的就是更容易看清它们的来源：|230859|//+Part+1.+Get+keys+from+one+of+the+Localizable.strings
perl+-ne+'print+"$1\n"+if+/%5E\s*(".%2B")\s*=/'+myapp/fr.lproj/Localizable.strings

//+Part+2.+Get+keys+from+the+source+code
grep+-n+-h+-Eo+-r++'NSLocalizedString$@(".*?")\s*,\s*nil$'+./+%7C+perl+-ne+'print+"$1\n"+if+/NSLocalizedString$@(".%2B")\s*,\s*nil$/'

//+Part+3.+Get+Part+1+and+2+together.

comm+-2+-3+<(grep+-n+-h+-Eo+-r++'NSLocalizedString$@(".*?")\s*,\s*nil$'+./+%7C+perl+-ne+'print+"$1\n"+if+/NSLocalizedString$@(".%2B")\s*,\s*nil$/'+%7C+sort+%7C+uniq)+<(perl+-ne+'print+"$1\n"+if+/%5E\s*(".%2B")\s*=/'+myapp/fr.lproj/Localizable.strings+%7C+sort)+%7C+uniq+>>+fr-localization-delta.txt|230860|输出文件包含在代码中找到但在Localizable.strings文件中找不到的键。下面是一个示例：|230861|"MPH"
"Map+Direction"
"Max+duration+of+a+detailed+recording,+hours"
"Moving+..."
"My+Track"
"New+Trip"|230862|当然可以改进得更多，但我还是想分享一下。|230863|entityMap^0|0|U|4|1K|3|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|16|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|19|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|J|7|1B|8|@]|9|@]|A|$K|L]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

Myself, I'm often carried away with coding, forgetting to put the entries into .strings files. Thus I have helper scripts to find what do I owe to put back into .strings files and translate.

As I use my own macro over NSLocalizedString, please review and update the script before using as I assumed for simplicity that nil is used as a second param to NSLocalizedString. The part you'd want to change is 

<pre><code>NSLocalizedString$@(".*?")\s*,\s*nil$ 
</code></pre>

Just replace it with something that matches your macro and NSLocalizedString usage.

Here comes the script, you only need Part 3 indeed. The rest is to see easier where it all comes from:

<pre><code>// Part 1. Get keys from one of the Localizable.strings
perl -ne 'print "$1\n" if /^\s*(".+")\s*=/' myapp/fr.lproj/Localizable.strings

// Part 2. Get keys from the source code
grep -n -h -Eo -r 'NSLocalizedString$@(".*?")\s*,\s*nil$' ./ | perl -ne 'print "$1\n" if /NSLocalizedString$@(".+")\s*,\s*nil$/'

// Part 3. Get Part 1 and 2 together.

comm -2 -3 &lt;(grep -n -h -Eo -r 'NSLocalizedString$@(".*?")\s*,\s*nil$' ./ | perl -ne 'print "$1\n" if /NSLocalizedString$@(".+")\s*,\s*nil$/' | sort | uniq) &lt;(perl -ne 'print "$1\n" if /^\s*(".+")\s*=/' myapp/fr.lproj/Localizable.strings | sort) | uniq &gt;&gt; fr-localization-delta.txt
</code></pre>

The output file contains keys that were found in the code, but not in the Localizable.strings file. Here is a sample:

<pre><code>"MPH"
"Map Direction"
"Max duration of a detailed recording, hours"
"Moving ..."
"My Track"
"New Trip"
</code></pre>

Certainly can be polished more, but thought I'd share.

blocks|key|3109791|text|如果有人在寻找Swift的解决方案。你可能想看看我在这里提出的解决方案:+SwiftyLocalization|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3109792|只需执行几个步骤即可在Google电子表格中实现非常灵活的本地化(注释、自定义颜色、高亮显示、字体、多张工作表等)。|3109793|简而言之，步骤是:+Google+Spreadsheet+-->+CSV+files+-->+Localizable.strings|3109794|此外，它还生成Localizables.swift，这是一个类似于键检索和解码接口的结构(您必须手动指定一种从键中解码字符串的方法)。|3109795|为什么这很棒？|3109796|3109797|你不再需要在所有地方都有一个普通字符串形式的键。|ordered-list-item|3109798|在编译时会检测到错误的键。|3109799|Xcode可以自动完成。|3109800|3109801|虽然有一些工具可以自动完成您的本地化关键字。对实数变量的引用将确保它始终是一个有效的键，否则它将无法编译。|3109802|//+It's+defined+as+computed+static+var,+so+it's+up-to-date+every+time+you+call.+
//+You+can+also+have+your+custom+retrieval+method+there.

button.setTitle(Localizables.login.button_title_login,+forState:+.Normal)|code-block|syntax|javascript|3109803|该项目使用Google+App+Script来转换工作表-->+CSV，并使用Python+script来转换CSV文件-->+Localizable.strings您可以快速查看此示例表，以了解其中的可能性。|3109804|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|1B|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|1E|8|@]|9|@]|A|$X|Y]]|$1|Z|3|10|5|6|7|1F|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|12|$]]

If anyone looking for a Swift solution. You may want to check out my solution I put together here: SwiftyLocalization

With few steps to setup, you will have a very flexible localization in Google Spreadsheet (comment, custom color, highlight, font, multiple sheets, and more).

In short, steps are: Google Spreadsheet --> CSV files --> Localizable.strings

Moreover, it also generates Localizables.swift, a struct that acts like interfaces to a key retrieval &amp; decoding for you (You have to manually specify a way to decode String from key though).

Why is this great?

<ol>
<li>You no longer need have a key as a plain string all over the places.</li>
<li>Wrong keys are detected at compile time.</li>
<li>Xcode can do autocomplete. </li>
</ol>

While there're tools that can autocomplete your localizable key. Reference to a real variable will ensure that it's always a valid key, else it won't compile.

<pre><code>// It's defined as computed static var, so it's up-to-date every time you call. 
// You can also have your custom retrieval method there.

button.setTitle(Localizables.login.button_title_login, forState: .Normal)
</code></pre>

The project uses Google App Script to convert Sheets --> CSV , and Python script to convert CSV files --> Localizable.strings You can have a quick look at this example sheet to know what's possible.

blocks|key|3109817|text|在Swift中，我使用了以下内容，例如本例中的按钮"Yes“：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3109818|NSLocalizedString("btn_yes",+value:+"Yes",+comment:+"Yes+button")|code-block|syntax|javascript|3109819|注意默认文本值的value:用法。第一个参数用作翻译ID。使用value:参数的好处是，可以在以后更改默认文本，但翻译ID保持不变。Localizable.strings文件将包含"btn_yes"+=+"Yes";|offset|length|style|CODE|3109820|如果没有使用value:参数，那么第一个参数将同时用于两个参数:转换ID和默认文本值。Localizable.strings文件将包含"Yes"+=+"Yes";。这种管理本地化文件的方式似乎很奇怪。特别是如果翻译的文本很长，那么ID也很长。只要更改了默认文本值的任何字符，转换ID也会随之更改。当使用外部翻译系统时，这会导致问题。翻译ID的改变被理解为添加新的翻译文本，这可能并不总是所希望的。|3109821|entityMap^0|0|0|8|6|V|6|2I|I|0|6|6|1V|E|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@$I|10|J|11|K|L]|$I|12|J|13|K|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$]]

In Swift I'm using the following, e.g. for button "Yes" in this case: 

<pre><code>NSLocalizedString("btn_yes", value: "Yes", comment: "Yes button")
</code></pre>

Note usage of the <code>value:</code> for the default text value. The first parameter serves as the translation ID. The advantage of using the <code>value:</code> parameter is that the default text can be changed later but the translation ID remains the same. The Localizable.strings file will contain <code>"btn_yes" = "Yes";</code>

If the <code>value:</code> parameter was not used then the first parameter would be used for both: for the translation ID and also for the default text value. The Localizable.strings file would contain <code>"Yes" = "Yes";</code>. This kind of managing localization files seems to be strange. Especially if the translated text is long then the ID is long as well. Whenever any character of the default text value is changed, then the translation ID gets changed as well. This leads to issues when external translation systems are used. Changing of the translation ID is understood as adding new translation text, which may not be always desired.

I'm (like all others) using <code>NSLocalizedString</code>to localize my app.

Unfortunately, there are several "drawbacks" (not necessarily the fault of NSLocalizedString itself), including

<ul>
<li>No autocompletition for strings in Xcode. This makes working not only error-prone but also tiresome.</li>
<li>You might end up redefining a string simply because you didn't know an equivalent string already existed (i.e. "Please enter password" vs. "Enter password first")</li>
<li>Similarily to the autocompletion-issue, you need to "remember"/copypaste the comment strings, or else <code>genstring</code> will end up with multiple comments for one string</li>
<li>If you want to use <code>genstring</code> after you've already localized some strings, you have to be careful to not lose your old localizations.</li>
<li>Same strings are scattered througout your whole project. For example, you used <code>NSLocalizedString(@"Abort", @"Cancel action")</code> everywhere, and then Code Review asks you to rename the string to <code>NSLocalizedString(@"Cancel", @"Cancel action")</code> to make the code more consistent.</li>
</ul>

What I do (and after some searches on SO I figured many people do this) is to have a seperate <code>strings.h</code> file where I <code>#define</code> all the localize-code. For example

<pre><code>// In strings.h
#define NSLS_COMMON_CANCEL NSLocalizedString(@"Cancel", nil)
// Somewhere else
NSLog(@"%@", NSLS_COMMON_CANCEL);
</code></pre>

This essentially provides code-completion, a single place to change variable names (so no need for genstring anymore), and an unique keyword to auto-refactor. However, this comes at the cost of ending up with a whole bunch of <code>#define</code> statements that are not inherently structured (i.e. like LocString.Common.Cancel or something like that). 

So, while this works somewhat fine, I was wondering how you guys do it in your projects. Are there other approaches to simplify the use of NSLocalizedString? Is there maybe even a framework that encapsulates it?

Best practice using NSLocalizedString

Python

Swift

Xcode

我(像其他人一样)正在使用NSLocalizedString来本地化我的应用程序。不幸的是，有几个“缺点”(不一定是NSLocalizedString本身的问题)，包括不自动完成Xcode中的字符串。这使得工作不仅容易出错，而且令人厌烦。您可能因为不知道已经存在一个等效的字符串而最终重新定义一个字符串(即“请输入密码”...

问使用NSLocalizedString的最佳实践
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用NSLocalizedString的最佳实践EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用NSLocalizedString的最佳实践
EN