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

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Bodo Meissner wrote:

> 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)


I would prefer to have this discussion on-list rather than on Bugzilla - 
it's easier.  Then, when we've all come to a decision and know where 
we're going then we can put stuff on Bugzilla.

> 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.


Okay, I see that now.

> 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.


I think that the intention all along has been to get each language into 
a separate file.  It was not this way from the beginning because as I 
worked on it it was easier for me to develop it all in one file.  I 
haven't broken it up yet because 1) we still only have a very few number 
of translations, 2) I just haven't taken the time yet, and 3) if we 
switch to gettext then a lot of that time will be wasted.

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


I do not disagree that gettext may be better-suited for these purposes.  
In fact, I investigated gettext when I first started doing the 
dictionary work.  My conclusion at the time was that it was too-big of a 
tool and too much work in using for our little purpose in translating a 
handful of lines for e-mailing.  Maybe I was wrong - I probably was - 
but even after spending a few hours reading gettext documentation I am 
no further (at all, really) into understanding how to actually use it 
for our purpose.

As infantile as the current dictionary approach may be I would like to 
point out that it apparently was a necessary step to generate enough 
interest and motivation to progress in this matter.  This bug report:

 http://bugs.hylafax.org/show_bug.cgi?id=176

Had gone nowhere for 4.5 years as it was.  We've come a long way in the 
last six months.

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


I'll try.  Please accept my apologies if I do in the future.  I am very 
accustomed to pressing "Reply All" when conversing with a group of 
people.  (And I actually like getting duplicate copies, myself, for 
posts directed specifically to me - as it raises my awareness to it.)

Lee.


____________________ 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*