On 09/03/15 13:11, CVAlkan wrote: > work with two specific fonts. I'll experiment a bit and see, but is that > true?
Yes, it only works with those two fonts. Which is why I said you'd have to rewrite it for Thai fonts. (BTW, can you recommend one or two _good_ Thai fonts? I can't tell if the fonts I'm using look bad, because they are bad, or if it has to do with the point size I'm using. I think I set the font size to 15 points. I know that below 12 points everything in Thai looks bad.) > Re: "You'll have to rewrite it for Thai fonts:" Looking at the oxt file, it > refers to StarBasic, but when unarchiving it seems to consist entirely of > headers unless I'm looking in the wrong place. I thought it was an FSF.hu project, which means that source code should be somewhere, if it is not included in the extension. I can't find an email address for Németh László, otherwise I'd ask him about source code. I can't tell, but a blog of his on LibreOffice.HU implies that he is no longer working on it, because LibO has built in support for what that extension does. But then my ability to read Hungarian is close to non-existent, so I'm probably mis-understanding it. (For some reason, the translator extension I use on my web browser, has decided that the blog is in English!) If you can read Hungarian, or your browser has a translation extension that works, you might glean more details on LibreOffice.HU. Nemeth has written a couple of blog posts on typography. How relevant they are to your specific situation, I don't know. :( >Where would I locate the source code for the routines the toolbar calls, what language do they use, and what compiler (or are they also interpreted?) would be required for a Linux installation? Those calls are probably to one or more LibreOffice APIs. Most of the LibreOffice code is C++, but there is some Python and Java. (LibreOffice hasn't quite yet banished all Java from the program. They are working on that, though.) I don't know what language the typography toolbar extension is written in. My choice would be Python, but C++ and Java are also candidates. (I obviously haven't looked at the source code for the extension.) If you're going to compile the extension, I'd suggest using the same process as for LibreOffice. >>> Re: "any source for documentation on how this genre of stuff is supposed to >>> work? >> AFAIK, not that non-programmers can understand." > So I would like to at least attempt to understand it - can you point me to > whatever you were referring to? I should have known you'd ask me that. And I've forgotten what the tool to use is. :( CLANG ( https://wiki.documentfoundation.org/Development/Clang_Code_Analysis ) might help you figure out why LibreOffice won't compile correctly. (This isn't the bug tool I mention below.) What I'm trying to remember, is the name of the tool that can be used to pull up code related to specific functions. In this instance, typography. The easy/hard way is to follow the instructions at https://www.libreoffice.org/about-us/source-code/ and https://wiki.documentfoundation.org/Development/How_to_build and then hope/pray/curse, that the source code is commented enough, that the typography related stuff is findable through using various command line tools, if you can't find anything with your usual IDE. Forget the claim about 26GB. You need at least 100 GB of free disk space. And don't run anything else on your computer, when doing the searches. Resource_Hogs-R-Us is their motto. I know that there is an easier way. I just don't remember what it is, or how to get there. :( This is really frustrating. There is/was an online tool, designed for bug hunting, especially by people reporting bugs, but it can be utilized for other things, including being semi-abused for this use-case. http://cgit.freedesktop.org/libreofficeis the GIT repository browser. Not quite what I was wanting, but helps segregate out the unwanted code, from the wanted code. I literally meant that the only documentation was the source code. Back when Sun ran OOo, there was a fair amount of documentation for most of the source code, but I don't know what happened to it. :( Documentation written by programmers, for programmers, to explain what was supposed to happen, and occasionally, functional equivalents, tests, and other useful things. It probably is still floating around, somewhere. Nothing useful if one was writing documentation, to explain how to use the software, though. jonathon -- To unsubscribe e-mail to: [email protected] 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/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
