Apache OpenOffice (AOO) Bugzilla – Issue 4555
Hyphenation works only for de_DE not for all de_*(Countries)
Last modified: 2012-02-20 02:24:17 UTC
If you use for e.g. the swiss-german dictionaries (de_CH) as default for your documents, the german hyphenation won't work. The german hyphenation should work for all de_*(Countries)||Dictionaries. de_DE, de_CH and de_AT will be available very soon.
Hi Peter, Have you thought much about taking the code in myspell that parses dictionary.lst and sharing it between our two projects (create a utility library that can be statically linked into both spell and hyphenator components). Then we could add lines in dictionary.lst like the following: HYPH de DE hyph_de.dic HYPH de CH hyph_de.dic Then you could invoke this code in the getLocales part of your hyphantor library and then use any customer added hyphenation dictionary (just like the spell library does with spellchecking dictionaries). This code is very simple to use and could easily be shared. We could also handle capitalization routines and things in similar ways. This would be an easy change and one that should help people to try their own hyphenation dictionaries. Please let me know if you are interested. Thanks, Kevin
Kevin, I was going to make XML-style configuration included in OpenOffice.Org configuration. I think that it is more openoffice'ish. Kevin?
Hi Peter, In the *long* run I have no problem with using xml but there are some drawbacks we should consider: 1. xml is harder for newbie users to manually edit correctly and many will want to make the install themselves since they have a dictionary (spell or hyph) that they want to use 2. xml is a pain for any indepedent automated installer to play with since it must really parse the appropriate xml to ensure syntax correctness and then write out the new xml. So I consider the dictionary.lst approach easier to deal with (what ever happened to simple .xxxrc files anyway), the code to do the dictionary.lst parsing already exists and does not depend on any other libraries but sal, and we can share some of the utility routines between the hyph, spell, and thesaurus, projects. So my suggestion for the near term is that we just use dictionary.lst for this now and then start worrying about interfaces to the configuration / xml code to do proper parsing and things later (something for release 1.2 or 1.3 timeframe). What do you think? Kevin
1. user doesn't need to edit them manually, since there will be configuration program. 2. If we make dictinstall to use openoffice's UDK there will be no problem to integrate it with openoffice configuration database. We need to make something like spadmin, but for installing deinstalling components (I use this word in generic sense, not openoffice's). This can be a core for installation program too.
The last message was about long run. for now 1. user doesn't need to change this files anyway. only developer. And developer can understand xml, because it's rather easy. 2. editing xml in separate file in known format isn't hard for dictinstall even if it doesn't know anything about xml. (we can make some extra comments like <!--dictinstall edits here, don't touch-->
Hi Peter, Agreed for the long term. But I do not think there is going to be any nice installer built with udk by volunteers for a while yet (very few non-Hamburg developers know or use the udk). The learning curve is steep (just using sal properly and not just ansi code for the thesaurus code took me a long time to get up to speed with). I simply do not have time to write one so unless you want to write it yourself and can have something working fast, why don't we keep that idea as an enhancement and simply just use dictionary.lst code we already have so that something is ready for OOo 1.0.X so people can start adding their own hyphenation dictionaries. It is panifully simple to use. Whereas even the componeent interface to the xml code would not be simple for most volunteers to learn and most do not want to learn or know sal and the udk. So that just leaves you and me! If you want to do it and can in a reasonable timeframe go for it. But if you are as time constrained as I am, why don't we take the simpler approach until we have some more time (later this summer for me after all of my classes and grading are completed). Thanks, Kevin
*** Issue 4687 has been marked as a duplicate of this issue. ***
Hi, I have fixed this for the upcoming OOo 1.0.1 so that you can register any hyphenation dictionary you want under any locale using the dictionary.lst So I am resolving this as fixed.
closing this