

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
28 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Re: stale processes a...| From | Sent On | Attachments |
|---|---|---|
| oth...@freeshell.org | Dec 21, 2004 1:57 pm | |
| Brian Candler | Dec 28, 2004 3:11 am | |
| Sam Varshavchik | Dec 28, 2004 4:16 am | |
| Paul L. Allen | Dec 28, 2004 11:32 am | |
| oth...@freeshell.org | Dec 28, 2004 7:45 pm | |
| oth...@freeshell.org | Dec 28, 2004 8:45 pm | |
| oth...@freeshell.org | Dec 28, 2004 9:02 pm | |
| Paul L. Allen | Dec 29, 2004 3:28 am | |
| oth...@freeshell.org | Dec 29, 2004 11:39 am | |
| Paul L. Allen | Dec 29, 2004 1:18 pm | |
| oth...@freeshell.org | Dec 29, 2004 2:34 pm | |
| Paul L. Allen | Dec 29, 2004 4:50 pm | |
| oth...@freeshell.org | Dec 29, 2004 9:08 pm | |
| Brian Candler | Dec 30, 2004 1:10 am | |
| Brian Candler | Dec 30, 2004 2:29 am | |
| Paul L. Allen | Dec 30, 2004 9:56 am | |
| Paul L. Allen | Dec 30, 2004 12:15 pm | |
| oth...@freeshell.org | Dec 30, 2004 2:39 pm | |
| oth...@freeshell.org | Dec 30, 2004 3:14 pm | |
| Paul L. Allen | Dec 30, 2004 4:07 pm | |
| Brian Candler | Dec 31, 2004 2:40 am | |
| Laurent Wacrenier | Dec 31, 2004 3:00 am | |
| Paul L. Allen | Dec 31, 2004 3:41 am | |
| Brian Candler | Dec 31, 2004 4:11 am | |
| Pawel Tecza | Dec 31, 2004 4:47 am | |
| Laurent Wacrenier | Dec 31, 2004 5:22 am | |
| Brian Candler | Jan 1, 2005 4:45 am | |
| Brian Candler | Jan 1, 2005 5:17 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [sqwebmail] Re: stale processes and m17n | Actions... |
|---|---|---|
| From: | oth...@freeshell.org (oth...@freeshell.org) | |
| Date: | Dec 28, 2004 9:02:05 pm | |
| List: | net.sourceforge.lists.courier-sqwebmail | |
On Tue, Dec 28, 2004 at 07:32:54PM +0000, Paul L. Allen wrote:
Brian Candler writes:
In that case, I think what is needed rather than a fixed ispell language per user, is the ability to select the ispell language from a drop-down list in the message composition screen.
That would be useful in multi-lingual environments, but the language preference sent by the browser should be pre-selected.
I think he said that a bit further up:
<quote>
Now, the choice of language here is given by the language which the user has set in their browser; and it also depends on you having installed templates for that language.
</quote>
Glad to know more people are finding the drop down menu idea useful =)
Does anyone know if there is a flag to ispell which will cause it to list all the available languages?
On some systems ispell is really aspell. And the aspell docs indicate it's going to be merged into pspell. The only way I can see of listing aspell languages is to go through its dictionary files, and the problem with that is they have names that start with things like "american" rather than using ISO language codes. Not insuperable, but at build time you'd have to detect what ispell really was and pick the appropriate look-up table (to be used at run-time because dictionaries may be added later).
Right, and, regardless of the speller being used, that config file similar to
"maildirshared" should be defined by the administrator. It seems simpler to do
so rather than having this configured and built during at the build stage. It
was my understanding that language selection was passed to aspell (not ispell)
by --lang=$CODE, wherein ispell you have the -d flag and the location of the
hashed dictionary. Regardless, a config file could work independant of the
speller, as long as SqWebMail is aware of which is being used (probably at the
configure stage of the build).
The qmailadmin method works. Looking at sources I have lying around, three years after the translation scheme was put in place there were 17 supported languages and four years after there were 19 supported languages (I suspect the slow-down in translations occurred because of lack of demand for other languages). Nineteen languages isn't a lot, but it's a lot more than sqwebmail has, and qmailadmin gets a lot less use than sqwebmail. I think that with a translation scheme along these lines we'd see a lot of translations appear in a matter of months.
I'm not familiar with how qmailadmin does its language templates, but I know the
ones for Sympa seem to work well. Maybe the qmailadmin and / or Sympa folk have
some insight on the subject. Having more translations for this fine piece of
software would be great.
Thanks for the discussion! It's nice to see people interested in this subject =)
!tr







