Hi Richard


You're asking hard questions about memory. My soft RAM is not what it used to be. Really softer. I remember the discussion but felt llike better minds would come to a better solution. I only mention this because every time I put more dictionaries on the server I get mail from Stefan asking how much more I intend to put up. :-)) So I know it is a sticky issue.

well
we are speaking about some Mb
not such a big deal imho

If Laurent can adapt for it, if there is es_AR and es_ES then they can both be installed.

Both can be installed
That is how professional terms spellchecker work (dutch medical)
the 2 files have to be registred for es_AR

But, here raises a key question
if i have a 'word" in es_ES, am I sure that this word is not written differently in en_AR

If this is the case (what i'm sure), then it is not possible as will have 2 proposals

The only thing to do is to have an Es_common
and es_ES, es_AR for specialized terms

Perhaps the best would be if es_AR is chosen then both es_ES and es_AR are installed and written into the dictionary.lst file, thereby getting a base language and the special, regional meanings.

technically possible
but brakes the logic of DicOOo
won't do it these days
can perharps be analysed and the .lst files enhanced
but need to think to compatibility issues ...

I do not want to hardcode a special behaviour for spanish

Would this accomplish the same benefit without too much re-working?

What i can propose is to upload the files as is

I'm actually rewritting DicOOo (well, lack of time these days). I'll try to take this into account and not brake the ile structure (adding a new column for inderiction)

Laurent

--
Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org
Indesko >> http://www.indesko.com
Nuxeo CPS >> http://www.nuxeo.com - http://www.cps-project.org
Livre "Programmation OpenOffice.org", Eyrolles 2004

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to