Apache OpenOffice (AOO) Bugzilla – Issue 97791
Add Yiddish to the language list box.
Last modified: 2013-08-07 15:02:13 UTC
I have built a Yiddish dictionary in hunspell format. The intellectual content is completely my own (continuing) effort, and I am willing to distribute this work according to the GPL. The dic and aff files are at http://www.cs.uky.edu/~raphael/private/yi.dic http://www.cs.uky.edu/~raphael/private/yi.aff I am sure that one could shorten the dic file by searching for common affixes, but I don't have software for that. I couldn't see how to integrate this dictionary into openoffice, because Yiddish is not in the list of languages it knows about.
I will add the necessary entry to the language list box, LangID 0x043D and ISO code mapping yi-IL are already available. @refoyl: please note that dictionaries as of OOo3 are handled with the extension mechanism, see http://wiki.services.openoffice.org/wiki/Extension_Dictionaries Please note also that the OOo license is LGPLv3, not GPL. Note to myself: Yiddish is written in Hebrew script and hence is RTL, needs an entry in the corresponding i18n method.
Thanks. The extension mechanism looks very general but very intricate; I don't think I can build a reasonable instance of that myself for Yiddish, so I will depend on you. Because Yiddish is not restricted to a single country, yi-IL is an acceptable name, but so would yi-US be. Is there no way to indicate country-independent languages? LGPLv3 is fine with me. I just want to make my work available! You can see a different view of my Yiddish list at http://www.cs.uky.edu/cgi-bin/cgiwrap/~raphael/dictionary.cgi ; it is driven from the same underlying data. I can also make available a Yiddish-transliteration dictionary for those who prefer to use a Romanized script. You are right that Yiddish traditionally uses a (modified) Hebrew script and is RTL.
Reassigning to spare time account.
In cws locales32: revision 273187 i18npool/source/isolang/mslangid.cxx svtools/source/misc/langtab.src @refoyl: > The extension mechanism looks very general but very intricate; I don't think I > can build a reasonable instance of that myself for Yiddish, so I will depend on you. If the wiki URL given above in #desc2 and looking at sample dictionaries don't help, please contact the dev@lingucomponent.openoffice.org mailing list to ask for help and improve documentation. > Because Yiddish is not restricted to a single country, yi-IL is an acceptable > name, but so would yi-US be. Is there no way to indicate country-independent > languages? The mapping of a LangID to a locale including the country is needed for implementation details. If you name your dictionaries and configuration entries just 'yi' that inicates the dictionary can be used with other locales of the same language as well, the dictionary service falls back to the installed dictionary of a language. > I can also make available a Yiddish-transliteration dictionary for those who > prefer to use a Romanized script. The same language in different scripts isn't supported yet.
Reassigning to QA for verification.
Verified in CWS locales32.
cmc->er: yi_US would have been better than yi_IL in retrospect as yi_US exists under glibc
OK in OOO320_m7. Closed. Note: I can see no Yiddish dictionary at http://extensions.services.openoffice.org/dictionaries If it shall be used by anyone, it should be there.
I re-opened, because I don't see the dictionary in http://extensions.services.openoffice.org/dictionaries
sba -> refoyl: Nice try :-) This issue was about OpenOffice not having the ability to set Yiddish. This is solved, thus this issue is done. Providing the dictionaty as .oxt in the extension repository is the job of the maintainer of the respective dictionary. Reading YOUR initial description makes me believe that uploading the extension is YOUR job. Feel free to submit a newly written issue to yourself and do not hi-jack this one for that purpose.. If you need help, follow the advice of erack. Setting this issue to fixed again.
And closed.
If you need any help in making the extension, I've mailed a sample based on the above dic+aff links.
As sba wrote, we should use another issue. Besides that, I suggest to do the following: I take the dic and aff files and create an extension in our build. The license is OK for that. Afterwards we can decide how to proceed with uploading.