>
> Ok, on second thought, I guess JSON is more consistent. If we want to
> allow ourselves extensibility in the future, we need to have an
> nesting level in the format. So it can't just be, eg,
>
> {
> "greeting": "hallo!",
> "exit": "goodbye"
> }
>
> It needs to be:
>
> {
> "strings": {
> "greeting": "hallo!",
> "exit": "goodbye"
> }
> }
>
Both look good.
>
> Also, unrelated. Many i18n frameworks have the ability to specify a
> comment about a string, so that translators know what it is intended
> to be used for. This seems like something we should have.
>
Most frameworks do that by using native comments. We could extend JSON with:
{
"greeting": [ "hallo!", "Greeting message" ],
"exit": [ "goodbye", "Going away message"],
}
or just say:
{
// Greeting message.
"greeting": "hallo!",
// Going away message.
"exit": "goodbye"
}
>
> - a
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
