X-mas gift for localization

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

X-mas gift for localization

Axel Hecht
Hi,

here is the Christmas gift for you:

We drop the requirement for the awkward \u1234-encoding stuff for
.properties files and allow the use of UTF-8 encoding there. There is no
requirement for the \:-encoding for the colon as well.


I won't approve these changes per-se, so this is currently only for open
trees, and if I were you, I wouldn't run for the trunk. So the practical
impact is small just now, but it will make things much easier in the
future. For those developing tools, you should support not changing
encoded strings, but once a string changes, you're not required to write
it back in encoded form.

Note, the encoding for .properties files is UTF-8 without BOM (byte
order mark).

Axel

PS: Of course this gift is for everyone, not just those that actually
celebrate Christmas.
_______________________________________________
mozilla-l10n mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-l10n
Reply | Threaded
Open this post in threaded view
|

Re: X-mas gift for localization

Ognyan Kulev
Axel Hecht wrote:
> We drop the requirement for the awkward \u1234-encoding stuff for
> .properties files and allow the use of UTF-8 encoding there. There is no
> requirement for the \:-encoding for the colon as well.

I'm glad that such distinction is made because our .properties files
already differ (in parsing) from Java .properties files.

Since this is no longer Java .properties file, it would be good if an
official name is announced for such .properties files, e.g. XUL
.properties or Mozilla .properties.

Regards,
ogi

_______________________________________________
mozilla-l10n mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-l10n
Reply | Threaded
Open this post in threaded view
|

Re: X-mas gift for localization

Axel Hecht
In reply to this post by Axel Hecht
Ognyan Kulev wrote:

> Axel Hecht wrote:
>> We drop the requirement for the awkward \u1234-encoding stuff for
>> .properties files and allow the use of UTF-8 encoding there. There is
>> no requirement for the \:-encoding for the colon as well.
>
> I'm glad that such distinction is made because our .properties files
> already differ (in parsing) from Java .properties files.
>
> Since this is no longer Java .properties file, it would be good if an
> official name is announced for such .properties files, e.g. XUL
> .properties or Mozilla .properties.

There is no need to name that child, though it may be a good idea to
actually put up an article with a grammar for those files on devmo.

I have put that on my todo list, though anybody is welcome to jump to it.

Axel
_______________________________________________
mozilla-l10n mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-l10n
Reply | Threaded
Open this post in threaded view
|

Re: X-mas gift for localization

Axel Hecht
In reply to this post by Axel Hecht
This is merely a policy change, the utf-8 decoder was in there for quite
some time, actually that was in 2000,
https://bugzilla.mozilla.org/show_bug.cgi?id=21418. Funny to see that it
wasn't really intended to do what it does :-)

Axel

David Fraser wrote:

> Axel Hecht wrote:
>> Hi,
>>
>> here is the Christmas gift for you:
>>
>> We drop the requirement for the awkward \u1234-encoding stuff for
>> .properties files and allow the use of UTF-8 encoding there. There is
>> no requirement for the \:-encoding for the colon as well.
>>
>>
>> I won't approve these changes per-se, so this is currently only for
>> open trees, and if I were you, I wouldn't run for the trunk. So the
>> practical impact is small just now, but it will make things much
>> easier in the future. For those developing tools, you should support
>> not changing encoded strings, but once a string changes, you're not
>> required to write it back in encoded form.
>>
>> Note, the encoding for .properties files is UTF-8 without BOM (byte
>> order mark).
>>
>> Axel
>>
>> PS: Of course this gift is for everyone, not just those that actually
>> celebrate Christmas.
> Wow, great news... AFAIR this was already possible, so is this only a
> policy change or was there code changed?
>
> Cheers
> David
_______________________________________________
mozilla-l10n mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-l10n
Reply | Threaded
Open this post in threaded view
|

Re: X-mas gift for localization

davidf (Bugzilla)
In reply to this post by Axel Hecht
Axel Hecht wrote:

> Hi,
>
> here is the Christmas gift for you:
>
> We drop the requirement for the awkward \u1234-encoding stuff for
> .properties files and allow the use of UTF-8 encoding there. There is
> no requirement for the \:-encoding for the colon as well.
>
>
> I won't approve these changes per-se, so this is currently only for
> open trees, and if I were you, I wouldn't run for the trunk. So the
> practical impact is small just now, but it will make things much
> easier in the future. For those developing tools, you should support
> not changing encoded strings, but once a string changes, you're not
> required to write it back in encoded form.
>
> Note, the encoding for .properties files is UTF-8 without BOM (byte
> order mark).
>
> Axel
>
> PS: Of course this gift is for everyone, not just those that actually
> celebrate Christmas.
Wow, great news... AFAIR this was already possible, so is this only a
policy change or was there code changed?

Cheers
David
_______________________________________________
mozilla-l10n mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-l10n