[Mono-devel-list] [PATCH] Reworked unified Locale classes

Kornél Pál kornelpal at hotmail.com
Fri Jun 17 05:47:41 EDT 2005

>From: Andreas Nahr
> I think the question which needs to be answered first is: Does it really
> make sense to translate all errormessages at all? Would we even be able to
> maintain these for a number of languages and which gain would we get from
> it.

If someone wants to traslate them he can do it. I personally don't want to
translate Mono to a bunch of languages.:) But I want to provide an
infrastructure that makes Mono able to be translated.

I attached my latest diff file (the same as in 2005-06-16 11:52 - Re:
[Mono-devel-list] [PATCH] Reworked unified Locale classes). Please have a
look at it if you haven't done it already.

It implements gettext () style resource management that means for me at
least that identifiers for non-English languages are the English texts and
no localization is done for English.

This implementation has minimal CPU and memory overhead compared to the
current version that does nothig. English messages are not stored in a
Hashtable just are returned as they were passed to GetText.

I think this is the best solution because it is based on the existing
localization infrastructure of Mono and I don't see any drawbacks that are
not in your conceptions.

Note that as I have written in my previous message even MS.NET uses a custom
ResourceSet for ResourceManager that don't load all the entries at
initialization. If we want to we can use a ResourceSet that does not cache
resources at all.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Locale.diff
Type: application/octet-stream
Size: 4870 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20050617/ede42a7d/attachment.obj 

More information about the Mono-devel-list mailing list