Dear list members,
On Fri, Apr 1, 2016 at 10:05 AM, Aleksandr Andreev
<aleksandr.andreev@gmail.com> wrote:
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?
To update, after some hacking around, I was able to bundle and
instlall the hyphenation patterns. It involved creating a
dictionaries.xcu file and a description.xml file. The simplest way
appears to be to crack open an existing extension with an archive
manager and take a look at how it is organized.
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?
Does anyone know the answer to this question? Can I set the
hyphenation character to be _ instead of -? Maybe in the locale data
files? If not, is this a bug against LO or a bug against Hunspell?
Thanks,
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.