[sldev] Looking at I18N formatting standards

[Tammy Nowotny]

I am not sure if there is a standard yet for time on other planets.  The 
only significant off-planet activities were the moon missions of the 
early 1970s, and those only lasted a few days each.  The astronauts just 
used earth time.  I don't know offhand if they used Houston Time or Zulu 
Time (same as UTC and GMT) or what.  The moon was so close and the 
speeds used to get there were so slow that relativity was insignificant.

Even when we just go to Mars, we have problems.  The second is a 
well-defined time unit our explorers would use that.  But Mars is far 
enough from the earth that you can't just use Earth time.  And of course 
its day and year are very different lengths from ours.

--Tammy Nowotny


Steve Bennetts (Steve Linden) wrote:
>>
>> l10n (localization):
>>> I am not particularly fond of indexed substitutions, I prefer 
>>> name/value pairs, because it gives the translator a little more 
>>> context, i.e. it is easier for a translator to look at "At [TIME] on 
>>> [DATE], there was [EVENT] on planet [PLANET]" then "At {1,time} on 
>>> {1,date}, there was {2} on planet{0,number,integer}."
>>>
>>> Our current compromise proposal would look something like this: 
>>>
>>> std::string bar(const LLSD& sdargs)
>>> {
>>>     LLUIString foo = getString("bar"); // bar = "At [DATE,time] on 
>>> [DATE,date], there was [EVENT] on planet [PLANET,integer]";
>>>     foo.setLLSDArgs(sdargs);
>>>     return foo.getString();
>>> }
>>