#Italics in lyx professional#

Surely for a vast majority of people writing in professional disciplines this issue of «hard formatting» as you put it (is that a technical term?) must come up frequently? Or perhaps they just give up at this point and go back to what they were doing before (LaTeX at one end of the spectrum, or Word at the other). Perhaps a lot of people simply don't make much use of these more advanced features, or produce full-length book-style documents with Writer. they cannot use Writer because of this limitation.Īctually I'm really surprised this isn't a bigger deal for more people. RGB wrote:, but it is clear that for many people this problem is a big problem. I think I'll persevere, for now, but I'll probably go back to LaTeX for the next one. Unfortunately this issue dramatically undercuts its usefulness. It's a shame, because this is the first time I've tried using OOo for a full-scale book like this, and I was really enjoying it, and considering recommending it to colleagues.

At least that way I can use the typeface I choose (Gentium, in this case, since it needs to be publishing-quality *and* support a lot of whacky characters!), with properly kerning italics etc. I could probably use combining diacritics (although, as I think about it, I suspect the macrons, for example, probably wouldn't line up nicely at all), and a few other typographical kludges, but as work-arounds go, I think I'd be better off just to give up and abandon the use of fields in favour of typing everything manually. The words I'm having difficulty with are, almost by definition, foreign words, which have complicated orthographies - for example, the first one I have need of is Saṃyuktāgama. In fact, as a work-around, it's almost equivalent to using an image of some text (e.g., in a given typeface) on a web site instead of text. They really shouldn't in this day and age, but they do.) The text cannot be searched (or copy-pasted, for example) anyway, since the string of underlying codepoints is completely different. Full-text indexing with Lucene/Solr springs to mind. This immediately creates a pile of problems (many programs, for example Java programs based on jflex, will choke on anything outside the BMP. The GNU Freefonts are populating section of the Unicode specification called 'Mathematical Alphanumeric Symbols,' which exists in the Supplementary Multilingual Plane (> U+FFFF). thanks for the creative suggestion, but I have to say - what an insane idea! I had to go check it out immediately! The 'hacker' in me loves this idea, but of course it's totally non-viable in practice.