[bind10-dev] internationalization for specification descriptions?

[Jerry Scharf]

Jeremy,

I agree with Michal on this. What I have seen done is that each message 
has a unique text string that is combined with the current language to 
find the correct translation in a file or database. It allows for things 
like different character sets within a given language as well as 
languages. I believe there is even some standard specification of this 
method, but I was only peripherally involved.

That way a crude translation involved picking the language you know and 
coming up with the translation for each message in the message set for 
your target.

This can/should be used to cover log messages and other message 
functions as well and the functionality will be required for the command 
tool.

Since we have a server local data store I would tend to toss it in 
there, but that is not mine to say.

jerry

On 10/15/2010 12:14 PM, Michal 'vorner' Vaner wrote:
> Hello
>
> On Fri, Oct 15, 2010 at 11:57:31AM -0500, Jeremy C. Reed wrote:
>    
>> Have we had any discussion on self documenting specifications (like
>> module_description or command_description) to be translated into
>> different languages? It would be easy to do and kept in same file.
>>      
> Having a way to translate the descriptions might be useful I guess. However, I'm
> not sure if keeping them in the files scattered around sources is the way to go,
> since the translator needs to find them all and edit them all. Furthermore,
> adding a language is nontrivial (need to patch the files, just unpacking the
> version translator had might break things if it is a different version).
>
> One part per translation (global, and doing some lookups) might be a better way?
>
> Have a nice day
>
>    
>
>
> _______________________________________________
> bind10-dev mailing list
> bind10-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind10-dev
>    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20101016/935cfffd/attachment.html>