ndt-users list created

[Alan Whinery <>]

Good Stuff!

IT occurs to me that not much more is required to respond based on the
language prefs specified by the browser in the HTTP header...

Richard Carlson wrote:
> Hi Jon;
>
> Way cool, thanks.
>
> Let me see if I understand what you did.  The text messages the applet
> prints have been moved to a separate 'text resource' file.  The applet
> code has also been modified to pull the text out of this file instead
> of having the text buried in the .java file.  The 'text resource' file
> has a list of tags and the text for that tag in a specific language
> (English and Norwegian for now).  To create a new translation, someone
> would just need to take an existing 'text resource' file and change
> the text strings for the appropriate tag.  To use this new tranlation,
> simply at the "language" tag into the .html file
>
> Does the applet need to be recompiled int the .jar file to use this
> new translation?
>
> I'll put this patch in the NDT contrib directory and will apply it to
> the main branch as well.
>
> This is really great!
>
> Rich
>
> On 12/9/2009 7:28 AM, Jon K Hellan wrote:
>> Hi
>>
>> For UNINETT's deployment of NDT, we've translated the applet into
>> Norwegian. We've finally
>> gotten around to separating the texts out into a Java resource files.
>> Patch based on ndt-3.5.6 is
>> attached. The resource files are included in the jar archive, so
>> deployment is easy.
>>
>> The default is English. If you want to display a different language,
>> add this to the
>> applet tag:
>>
>>    <PARAM NAME="language" VALUE="nb">
>>    <PARAM NAME="country" VALUE="NO">
>>
>> If you want to translate to, e.g. French in France, make a file
>>
>> Tcpbw100_msgs_fr_FR.properties, and go ahead with translation. In
>> this case, the tag would be:
>>
>>    <PARAM NAME="language" VALUE="fr">
>>    <PARAM NAME="country" VALUE="FR">
>>
>> Accented characters must be entered as unicode literals.
>>
>> Regards
>>
>> Jon Kåre Hellan, UNINETT, Norway