Hi all, R.J. Baars wrote:
> The use of the 'all'-dictionary will require validation by all language > teams. And, as mentioned before, the flexes could quite different. You got me wrong! I don't want anyone to provide a 'language-all' dictionary by default. What I do like is to have hunspell support them. If that were the case AND if user-dictionaries were compatible with hunspell, THEN the user himself can add words/names to some very personal 'language-all' user-dictionary. Thats what my concern is about. A 'language-all' dictionary provided by default is a little bit questionable since I don't really know for example how e.g. English names are written in Chinese or Japanese. Probably one of both will happen there: 1) The name is written as in English if the readers can understand that 2) The name will be written in Chinese or Japanese characters in a way that, when read, they will sound like when that name is read in English. Only in the first case it will be ok to have names already supplied in a 'default' dictionary. Thus the choice should probably be on the users side. And that could best be done if it is him who makes those entries. Also the vice-versa approach, having Chinese names romanized won't work well with a 'languag-all' dictionary since there are more than one method to romanize Chinese or Japanese names. Here also the best choice will probably be to leave that to the user. Regards, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
