<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jeremy,<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Since we have a server local data store I would tend to toss it in
there, but that is not mine to say.<br>
<br>
jerry<br>
<br>
On 10/15/2010 12:14 PM, Michal 'vorner' Vaner wrote:
<blockquote cite="mid:20101015191446.GA9408@hydra.kolej.mff.cuni.cz"
type="cite">
<pre wrap="">Hello
On Fri, Oct 15, 2010 at 11:57:31AM -0500, Jeremy C. Reed wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
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
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
bind10-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bind10-dev@lists.isc.org">bind10-dev@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind10-dev">https://lists.isc.org/mailman/listinfo/bind10-dev</a>
</pre>
</blockquote>
</body>
</html>