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

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Dimitrios wrote:

> On Tue, 27 Jun 2006 19:36:20 +0200 Bodo Meissner <bodo@xxxxxxxxx> wrote:
>
>  
>
> > I think using quoted printable would make it harder to edit the  
> > dictionary file. IMHO UTF-8 may be better.
> >    
>
> i already suggested this. UTF-8 should be the way to do all language translations.
>
> unfortunately the developers from the US said they don't like UTF-8 since they don't really need it.
>  

As I think that I was the only one of "the developers" that had any 
comments directed towards your report I think that it's better to not 
taint the rest of "the developers" with my bias.  In any case, let me 
clarify again what I said...

In reviewing e-mail usage I just don't see MUAs using UTF-8, and I'm not 
keen to have HylaFAX mailing scripts be independently righteous in its 
character set usage... simply because HylaFAX isn't about setting e-mail 
trends.

In fact, the e-mail that you sent to the list just now didn't even use 
UTF-8...

 Date: Wed, 28 Jun 2006 00:57:05 +0300
 From: Dimitrios <sehh@xxxxxxxxxxx>
 To: hylafax-users@xxxxxxxxxxx
 Subject: Re: [hylafax-users] wrong charset in notification mail - suggest CHARSET in bin/dictionary
 Message-ID: <20060628005705.4c8e3b45@ekolaptis.>
 In-Reply-To: <1151429780l.19046l.1l@natira>
 References: <1151399190l.8095l.13l@natira>
	<02f801c699ee$44fa7a50$570a000a@dazza>
	<1151429780l.19046l.1l@natira>
 X-Mailer: Sylpheed-Claws 2.3.0 (GTK+ 2.8.19; x86_64-redhat-linux-gnu)
 X-Face: .iV@#jGqofFsTT&Ywao5Ix!";_!YWN.+cQ?vv1BvIYSP0[wjsf_jz}fzR9=.sUD&j\e0;5)1g!DLTa<Uq6lDKD53#S`d2dED%Bcx]@U*Fv/+k8wH<n&\Xd&?pm~A8};#PPAN)~4<U^{@(6#SUOs|bZo%c8djR}MW(|%WYG4DPyY\Do2tECcyWy)\j~y3~H{r.`n0D1R=)gq*(xA/zN[i(L@,A%z"FY>/G)CZ
 Mime-Version: 1.0
 Content-Type: text/plain; charset=US-ASCII


This is what I'm getting after.  Sure, uniting the world with UTF-8 is a 
wonderful ideal.  As soon as everyone else begins doing that we should, too.

> > With a growing number of languages I would prefer a different file for  
> > every language, maybe in language specific directories.  This would  
> > make it easier to edit and compare the message sets and it would avoid  
> > problems with mixed charsets in one file. I would also prefer seperate  
> > files because this allows using different charsets.
> >    
>
> The proper way is "gettext". Its the acceptable standard for translations, used by all major open source projects (from Linux distributions like Fedora, to window/desktop managers like KDE and GNOME).
>
> Unfortunately, i was told by the developers that they didn't like this as well, so we are stuck with a dictionary file that isn't compatible by any translation tool (like KBabel and GTranslator).

Again, "the developers" to which you refer probably is only me.  Let's 
be fair to the others.

And, in all honesty I didn't say that I didn't like gettext - but that I 
didn't know anything about gettext and that I needed you or someone to 
teach me about it, possibly even writing some coding suggestions, so 
that I could have an educated opinion about it.

I did a few hours of independent research on using gettext and from what 
I saw there didn't appear to be anything magical at all about what 
gettext does.  It takes a string of text in one language and finds its 
match in a set of "word lists" of sorts... not that dissimilar to what 
we're doing already.  The only functional difference that gettext would 
get us - that I could see - is that it would make us look "cool" in 
gettext zealots' eyes and would permit translators to use cool 
gettext-oriented tools (instead of a text editor).

So, I'm open to discussing both of these issues if you would like to 
participate in that discussion rather than backing out at even small 
objections.

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*