Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Dear list members,

I'd like to create a hyphenation dictionary for Church Slavonic
(Church Slavic), ISO code CU. I have ported the existing TeX patterns
using the instructions here:
https://wiki.openoffice.org/wiki/Documentation/SL/Using_TeX_hyphenation_patterns_in_OpenOffice.org

(are these the correct instructions to use? I have not found anything newer.)

Now, it's not clear to me what I need to do with the resulting .dic
file. The documentation says I need to bundle it as a Dictionary
Extension. But is there documentation on how that needs to be done?
After some digging around, I found this:
https://wiki.openoffice.org/wiki/Extension_Dictionaries

But it doesn't really say what to do. It just gives some XML code.
Some guidance would be appreciated!

Second question. The character commonly used in Church Slavonic for
hyphenation is the underscore, not the hyphen (e.g., hyphe_nation). In
TeX, I can simply set the hyphenchar to be _. Is this possible in
LibreOffice? If yes, where do I specify it?

Thank you for your help!

Aleksandr

-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.