Re: [hylafax-users] wrong charset in notification mail - suggest CHARSET in bin/dictionary

[Bodo Meissner <bodo@xxxxxxxxx>]

Hello Lee (and others who want to participate),

first a general question:
Should we discuss this here in the mailing list or as comments in a  
bugzilla report?
(http://bugs.hylafax.org/show_bug.cgi?id=777)

Am 27.06.2006 19:47:07 schrieb(en) Lee Howard:
> Bodo Meissner wrote:
>
> > I think using quoted printable would make it harder to edit the   
> > dictionary file.
>
>
> Ideally the dictionary file should not be edited.  Customizations  
> should be placed in etc/FaxDictionary.

I did not think of editing for customization purposes.

> But for those who do edit the
> dictionary file - for example to add a language or to correct a  
> translation - if they have an evil text editor it may not handle the  
> non-ascii characters well.

That's just what I meant.

If we have different encodings in one file I must somehow tell my  
editor to correctly display the encoding for a language I want to add  
or change. This will at least show funny characters in other languages  
that use a different encoding. And maybe the editor wants to "fix"  
something in other languages.
I assume the translations will be based on English version, but  
sometimes it can be useful to check other languages to find out which  
of several possible translations is correct or best for a specific  
message. This will be more difficult if the other language is in a  
different encoding than the language I want to edit.

Having one large file with all languages makes it more difficult to  
compare different languages.
Assuming we have to add some new messages to the dictionary, the author  
of the change would probably add them to the English version and other  
languages he speaks. Then other translators have to supply the messages  
in other languages. In order to check if the dictionary is complete for  
all languages, I would like to extract a sorted list of the dictionary  
variables for every language and do a diff to find any missing  
messages. This would be much easier with separate files.

If we used standard methods (gettext as suggested by Dimitrios) there  
would be tools already available for this purpose.


Bodo

P.S.:
Don't send me a copy of your reply, I'm subscribed to the mailing list.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*