281
edits
Changes
Jump to navigation
Jump to search
m
[TODO: describe {{todo|Describe where to check for it, perhaps write a wiki page for every encoding.]}}
[TODO: provide {{todo|Provide a more comprehensive overview and more complex examples]}}
[TODO: {{todo|<code>enco-acc.tex]</code>}}
[TODO]{{todo|Something goes here.}}
[TODO: this {{todo|This is probably also possible]. (Yes, it is; see the "verbatim end-of-line character" page for an example. --Brooks}}
[TODO: how {{todo|How to use \<cmd>crop]</cmd>}}
[TODO: comments {{todo|Comments about the following code and some more examples:].}}
[TODO]{{todo|Something goes here.}}
Added backlinks, a bunch of TODO tags in place of TODO text.
< [TODO, perhaps [Main Page]] | [[Visuals]] > {{todo|Perhaps give another title to this page, perhaps accented characters]}}
== . ==
First of all: make sure that you are using the proper encoding and the proper regime (see slso [[Encodings and Regimes]]). Most problems can already be solved by deciding for the proper encoding (or by making one by your own).
You have to be aware that a word with faked glyphs cannot be hyphenated and the the resulting PDF won't be fully searchable either.
However, some of them may be missing in the encoding you use, so make sure that the accent you want is available in the encoding first.
=== Defining a shortcut ===
== Drawing characters ==
đ/Đ (U+0110/0111, "latin small/capital letter d with stroke") are glyphs present in very few encodings. On the other hand, only a straight line has to be drawn in order to fake the glyph. Although it is difficult to position this line (stroke) properly for a general case and despite being far from optimal, it can be sometimes useful to have such a little hack. Here's an example of how \dstroke and \Dstroke were faked:
=== Drawing with metafun ===
=== Cropping existing characters ===
== Rotating/mirorring characters ==
<texcode>
[[Latin Modern Roman]] for example happens to have over 600 glyphs, so it may be that your favourite glyph (such as <code>udoublegrave</code>) is already there, but you can't access it using standard encodings. In this case you can write your own encoding and support for it. This way takes some more effort and skills than all of the above mentioned solutions and it also takes additional effort if you want to compile the document on another computer. But unless you are using [[XeTeX]], [[Aleph]], ... or any other TeX system which got rid of the 256-glyphs-limit, this is the only proper way if you're opting for high quality.
[[Category:Fonts]]
[[Category:International]]
