28 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Spelling and other te...
FromSent OnAttachments
oth...@freeshell.orgDec 21, 2004 1:57 pm 
Brian CandlerDec 28, 2004 3:11 am 
Sam VarshavchikDec 28, 2004 4:16 am 
Paul L. AllenDec 28, 2004 11:32 am 
oth...@freeshell.orgDec 28, 2004 7:45 pm 
oth...@freeshell.orgDec 28, 2004 8:45 pm 
oth...@freeshell.orgDec 28, 2004 9:02 pm 
Paul L. AllenDec 29, 2004 3:28 am 
oth...@freeshell.orgDec 29, 2004 11:39 am 
Paul L. AllenDec 29, 2004 1:18 pm 
oth...@freeshell.orgDec 29, 2004 2:34 pm 
Paul L. AllenDec 29, 2004 4:50 pm 
oth...@freeshell.orgDec 29, 2004 9:08 pm 
Brian CandlerDec 30, 2004 1:10 am 
Brian CandlerDec 30, 2004 2:29 am 
Paul L. AllenDec 30, 2004 9:56 am 
Paul L. AllenDec 30, 2004 12:15 pm 
oth...@freeshell.orgDec 30, 2004 2:39 pm 
oth...@freeshell.orgDec 30, 2004 3:14 pm 
Paul L. AllenDec 30, 2004 4:07 pm 
Brian CandlerDec 31, 2004 2:40 am 
Laurent WacrenierDec 31, 2004 3:00 am 
Paul L. AllenDec 31, 2004 3:41 am 
Brian CandlerDec 31, 2004 4:11 am 
Pawel TeczaDec 31, 2004 4:47 am 
Laurent WacrenierDec 31, 2004 5:22 am 
Brian CandlerJan 1, 2005 4:45 am 
Brian CandlerJan 1, 2005 5:17 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] Spelling and other templates (Was: stale processes and m17n)Actions...
From:oth...@freeshell.org (oth@freeshell.org)
Date:Dec 29, 2004 2:34:21 pm
List:net.sourceforge.lists.courier-sqwebmail

On Wed, Dec 29, 2004 at 09:18:47PM +0000, Paul L. Allen wrote:

[Figuring out which spelling checker is in use and which dictionaries are available]

Shouldn't take that long =)

That's why I suggest the determination be left up to the administrator, who can discern which dictionaries are installed and write a config file appropriately. Then it doesn't matter what the name of the dictionary is, because its location or language code is entered to a file with a title for that language. Ex:

Many administrators would need documentation on how to do that because delving through the spelling-checker docs on how to go about it would take a while. If you're going to document it you might as well script it.

Is there any more docu needed than what's already been written? It seems simple
enough to me anyway. Figuring this out for SqWebMail is no different than any
other mail client. You figure out what flag feeds the speller and the location
of the dictionary or language code. It's pretty straightforward. Hell, if an
admin can't do that, that admin probably couldn't get the server started in the
first place.

I see the scripting method being possible, but altogether messy and will take
much longer to test and implement before becoming "stable" rather than putting
an extra paragraph in the docu and making people read it if they want m17n. I'm
just imagining the multitude of problems possibly ensuing in a system such as
pkgsrc that runs on 13 or so different platforms.

If you want to automate it, make it work first. Have the functionality and add
the automation later. Or add it now with a BUILD_DEF like BUILD_LANG_LIST
(yes|no) so that admins can either build it themselves or let the build process
do it.

I can see why you'd like this to be totally automated and built at build time by configure, Makefiles, patches, etc. However it does seem a bit more work than just allowing a human to do it.

One human at each of thousands of ISPs. It's a lot of duplicated effort. With many of them not knowing enough to figure out how to do it and end up asking here for idiot-level instructions. So eventually it will get scripted just to stop the bandwidth being wasted by people who can't figure out where their spelling checker keeps its dictionaries, because once you have idiot-level instructions you can script it.

For a functionality that doesn't currently exist? If the file doesn't exist,
SqWebMail defaults to English and if the file does exist SqWebMail reads it and
makes the appropriate changes to the UI. Just like maildirshared and
logindomainlist. The only effort needed is when admins want to add spelling
m17n...and at that point they'd probably bust out the manual anyway.

If you run into an admin who can't discern which speller is installed, which
dictionaries are installed and their respective language codes or files, and how
to put this info into a text file - after installing and configuring this
package, having the blurb in the docu and access to the list archives - please
let me know. I'd be more than happy to give a basic tutorial of the filesystem
and pkg mgmt system for the sake of m17n.

I'm not familiar with how qmailadmin does its language templates, but I know the ones for Sympa seem to work well.

I'm not familiar with that. Maybe it's better suited to sqwebmail than the qmailadmin way of doing things.

http://www.sympa.org/howtotranslate.html

Seems that if one followed those instructions the templates would be built automagically?

If I understand it correctly, to use it in sqwebmail would STILL require template substitution.

Yes, it does seem that way in the Sympa templates.

In essence you have to do everything that the qmailadmin system does and THEN call gettext on top.

Based on your analysis, it seems that qmailadmin's method is superior.

Another way would be to abandon templates and have all the html generated on the fly by the code. That would eliminate the template substitution step. But then you lose the ability to easily change the look and feel of the page - you have to hack code instead of html and most people who are good coders are not good at page design/layout (and vice versa).

I had the same thought process and came to the same conclusion =)

So unless I'm missing something, using gettext would make it harder for anyone who wants to customize things.

Maybe that's why qmailadmin has more translations than Sympa?

!tr