On Dec 23, 2009, at 7:38 AM, Jerry Krinock wrote:
>
> Well, Ricky I see you're one of the few who has really thought through all
> the issues.
>
> On 2009 Dec 22, at 19:59, Kyle Sluder wrote:
>
>> On Tue, Dec 22, 2009 at 11:54 AM, Ricky Sharp wrote:
>>> * No plural forms (while allowing plur
2009/12/23 Jerry Krinock :
>
> I read somewhere that in some languages, for example Arabic, there are
> actually different forms for "one", "two", and "three or more".
Localizing plurals is hard because the plural rules for different
languages are complex. Just stay away from plurals if you can.
On Tuesday, December 22, 2009, at 09:59PM, "Kyle Sluder"
wrote:
>On Tue, Dec 22, 2009 at 11:54 AM, Ricky Sharp wrote:
>> (2) Externalize all strings from the nibs and put them into
>> Localizable.strings. This allows me to have a single file to hand off to
>> translators. I can also group
Well, Ricky I see you're one of the few who has really thought through all the
issues.
On 2009 Dec 22, at 19:59, Kyle Sluder wrote:
> On Tue, Dec 22, 2009 at 11:54 AM, Ricky Sharp wrote:
>> * No plural forms (while allowing plurals can be handled, it's not worth the
>> effort IMO)
That's goo
On Tue, Dec 22, 2009 at 11:54 AM, Ricky Sharp wrote:
> (1) Have separate nibs for each language. I agree with those that say you
> cannot have a one-size-fits-all layout. Each nib will thus carry layout,
> font size, style, etc. that makes sense for a particular language.
Luckily this isn't a
Thank you all for the replies.
Here's my final plan:
(1) Have separate nibs for each language. I agree with those that say you
cannot have a one-size-fits-all layout. Each nib will thus carry layout, font
size, style, etc. that makes sense for a particular language.
I've already "pseudo-loca
On Dec 21, 2009, at 8:18 PM, Uli Kusterer wrote:
On 20.12.2009, at 21:30, Ricky Sharp wrote:
Thus, I'm wondering if it would ultimately be worth it to
externalize all strings from my nibs and just put everything in my
single .strings file. This will clearly involve me adding tons of
IBOut
On Dec 21, 2009, at 8:18 PM, Uli Kusterer wrote:
> On 20.12.2009, at 21:30, Ricky Sharp wrote:
>> Thus, I'm wondering if it would ultimately be worth it to externalize all
>> strings from my nibs and just put everything in my single .strings file.
>> This will clearly involve me adding tons of I
On 20.12.2009, at 21:30, Ricky Sharp wrote:
> Thus, I'm wondering if it would ultimately be worth it to externalize all
> strings from my nibs and just put everything in my single .strings file.
> This will clearly involve me adding tons of IBOutlet ivars just so that at
> runtime I can set the
On 2009 Dec 21, at 01:27, Symadept wrote:
> Now pass these files to Localization
> team and they shall simply copy paste the other version of the string in RHS
> of the corresponding files.
Well, of course there are tools for this. I use and recommend Max Seelemann's
Localization Suite, and ju
Just my 2c gained from translating UIs in french. Localized strings can show a
great variation in length even among close languages such as english and
french. Moreover, english allows for short sentence/syntax whereas french does
not, at least not easily.
From what I've seen, there are two str
Hi Ricky,
Even in my one of the project I am doing the same. Localizable.strings
(english) version shall have all the strings in Key-Value pair format,
"Hello" = "Hello"; And you can keep the comment on top of the string /*
Welcome text */.
And you can have many IBOutlets to set the string at run
In getting quotes from many localization companies, I've found that some have
different processes. For example, one company would prefer if I just provide
.string files. During their QA process, they'll then run the app and look at
everything in context.
While generating .strings from nibs i
13 matches
Mail list logo
