I just noticed that iPhoto string table entries have the following form:
Key1 = "Value1";
Not that it make any difference. Just interesting.
--Richard
On Aug 6, 2010, at 9:50 AM, Richard Somers wrote:
String table entrys have the following form.
"Key1" = "Value1";
__
In addition to context, another consideration is refactoring ... IE: over
time, you may change the text, even in the primary language. If that be the
case, your message will not match your key anymore (unless you change your
code ... which seems counterproductive).
I tend to use keys like:
Hey Richard!
On 6/Aug/2010, at 8:50 AM, Richard Somers wrote:
> It appears that literal keys would easier to translate because no cross
> referencing would be required. Why then are symbolic keys also used?
I think it's a matter of choosing what works best for your workflow and all
parties invo
On 2010 Aug 06, at 09:05, Dave DeLong wrote:
> Sometimes a word in your original language can have multiple translations,
> depending in the context.
Yes. Example:
/* Name of a preference tab which contains preference settings for how things
look when they are viewed. This is intentionally
Sometimes a word in your original language can have multiple translations,
depending in the context. Where I work, we use symbolic keys so that we can
allow for context-sensitive translations.
Dave
Sent from my iPhone
On Aug 6, 2010, at 9:50 AM, Richard Somers wrote:
> String table entrys h
