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


On 28/10/16 22:26, CVAlkan wrote:

Would love to see it when you have a prototype ...

Instead of creating a program from scratch, I'm going to modify an
existing one. The downside is that I have to learn another programming
language. Along the way, I'll also have to fix some existing bugs in
that program.

The reason for modifying the existing program, is that it means I have
to write one routine (^1) to display the metadata that it currently reads.

Once I've finished that modification, I'll modify a different tool, to
write valid metadata to each glyph.

I don't have a time frame by which this will be done.

I'm in the midst of two major projects, and one minor project.  However,
one of those projects requires LibO to recognize, and correctly display
different writing systems in the same phrase.
(So this is, in effect, becomes a sub-project of one of those projects.)

^1: That is the theory. In practice, I expect to have to fix half a
dozen bugs, and, maybe implement one or two other functions.

jonathon

-- 
To unsubscribe e-mail to: users+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/users/
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.