On 11/03/15 19:48, CVAlkan wrote: > LibreOffice, development relies entirely on a volunteer who happens to have
There are a couple of paid developers. Their coding priority is what ever the organization that pays them, tells them to do. At least one of the firms that offers paid support, automatically submits all fixes for clients, into the LibreOffice code. Sometimes those bigfixes are long-standing issues in Bugzilla. Sometimes they are things that nobody noticed as problem, until their client said: "fix it". I _think_ that some of the support firms let their developers select a bug to fix, when their paying clients don't have any bugs that needed to be fixed yesterday. > characteristics, some knowledgeable user/tester/guinea pig(s) would need to > be available. Given the statistical improbabilities there, I suppose we live I've forgotten who it is, but somebody (¿QA?, ¿Developer? I really don't remember) is actively looking for things that have been broken, to test, either to ensure that the fix worked, or to find out what breaks, the first build after the code merge is completed. The critical datapoint here, is that the testing must be completely automated. No babysitting allowed. I think it is the same individual that is collecting documents, simply to open, look at whether or not they "break", close, and go onto the next one. If/when this type of testing can be automatized, it is automated. Edge cases that are rare, but break things, are specifically welcome. > Nonetheless, here is a list of some fonts to look at (all are free). Thanks for the list. > FreeSerif (In a class by itself) I'll take a look at it. > your own custom language combinations using FontForge or something similar, > although I haven't tried that. I've customized some fonts with FontForge. Not something I'd like to do with umpteen glyphs, though. > Mixing Thai font glyphs with Western glyphs is complicated because of the > way Thai characters are formed. There is no upper case, so the shift key > just gives you access to additional, less frequently used characters, but > there are tall and short letters that can appear to non-Thai speakers as > capitals. And when those tall letters pop up in the middle of the word, the non-Thai readers wonder what is wrong with the spelling, or grammar-checker, try to fix it, and find that they cant, but don't know what is preventing them from doing so. >Several (though not all) vowels in Thai are symbols placed above or below the consonents they are joined with. Coupled with the fact that Thai not only has what we would call accents, but - being a tonal language - has tone marks that can also go above some syllables. One of these days, I'm going to figure out how to get styles to only affect specific glyphs. Then create one style for tone marks, one style for accents, and one style for the other non-basic glyph stuff. Basically, give everything their own colour. It is amazing how the errors pop out, when that colouring is done. > but if the two languages are mixed in the same line, getting things to look clean takes a > bit of planning when choosing what fonts to use. Not just in fonts, but also minor modifications of the styles that are used. One reason I insist on language specific styles, is because that is the only way to ensure that things stay the way they should, when creating multilingual content. > The best way to illustrate this is to download the Thai Font Book at > http://ftp.opentle.org/pub/national-fonts/FONTBOOK.PDF. Thanks. Looks very useful, especially to get an idea of what Thai esthetic norms are. > descenders, x-height and such things are defined. The very next page shows > how to line up Thai and western characters next to each other in order to > look good. The illustrations are very numerous and very well done. Looked to me like somebody was really tired of seeing bad alignment of those writing systems, and wanted people to stop putting out bad work, when it as easy to do good work. > together, FreeSerif is (again, so far as I am aware) the only go-to font > that will let you do that. Code2000 is an ugly pan-unicode font that has fairly sensible fallbacks. There are a couple of pan-unicode fonts, but they tend to be "ugly". I did see one that was very pretty, but the price tag wasn't.(US$100,000 per weight.) > earlier posting from a year or so ago to whatever resources the doc team > might eventually use to document font usage in LO?? Thanks. Almost convinced me to find your material from last year, and add it to this, then post it to my LibreOffice blog. I've been meaning to restart it, especially now that I'm writing material in multiple languages, and writing systems, again. 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
