Search results

Create the page "Encodings and Regimes" on this wiki! See also the search results found.

Page title matches

• Encodings and Regimes - Old Content
  ...and will only deal with 256 characters per font. Similarly, "legacy" file encodings on current operating systems (e.g. Latin-1, Mac Roman, Windows 1252, ISO-88 ...ants, from [[Omega]] over [[XeTeX]] to [[LuaTeX]], dropped that limitation and work with full Unicode character sets, in fonts as well as in your source d
  15 KB (2,430 words) - 13:17, 9 August 2020
• Encodings and Regimes in XeTeX
  ...interested in details about how XeTeX deals with input encodings and font encodings. (I've dropped a couple of notes here before I forget them.) = Input Encodings (Regimes) =
  5 KB (835 words) - 12:51, 7 June 2020

Page text matches

• Second Step
  % (in LuaTeX and XeTeX, UTF-8 is on by default, thus not needed) ...you don't need that line any more. (More on that topic in [[Encodings and Regimes - Old Content]].)
  2 KB (238 words) - 13:19, 9 August 2020
• Languages
  Today, with the international use of the UTF-8 standard for input and output encoding, you only need two commands, with the '''[[#Language tags|l :: and to change the hyphenation rules, quotation marks, all that sort of thing, t
  3 KB (375 words) - 08:28, 2 July 2022
• Faking characters
  In TeX you can only access 256 glyphs at a time (With XeTeX and LuaTeX, it's over, thanks to UTF-8 support). Well, but even if you could ac ...using the proper encoding and the proper regime (see slso [[Encodings and Regimes - Old Content]]). Most problems can already be solved by deciding for the p
  5 KB (762 words) - 13:25, 9 August 2020
• Encodings and Regimes in XeTeX
  ...interested in details about how XeTeX deals with input encodings and font encodings. (I've dropped a couple of notes here before I forget them.) = Input Encodings (Regimes) =
  5 KB (835 words) - 12:51, 7 June 2020
• Fonts - Old Content
  ...g fonts are [[TypeScripts - Old Content]].''' It’s a system of abstraction and aliases, which may seem “strange” at first for new users of ConTeXt. ...en to use [[XeTeX - Old Content]] then you can forget almost all the magic and start using your system fonts (see [[Fonts_in_XeTeX - Old Content]]).
  6 KB (976 words) - 08:26, 2 July 2022
• Encodings and Regimes - Old Content
  ...and will only deal with 256 characters per font. Similarly, "legacy" file encodings on current operating systems (e.g. Latin-1, Mac Roman, Windows 1252, ISO-88 ...ants, from [[Omega]] over [[XeTeX]] to [[LuaTeX]], dropped that limitation and work with full Unicode character sets, in fonts as well as in your source d
  15 KB (2,430 words) - 13:17, 9 August 2020
• MkIV Differences
  ...e intentional as well as the unavoidable incompatibilities between Mark IV and Mark II (but not bugs). ...ifferently. You must remember to always give the full name of the options, and then the effects should be almost unnoticeable.
  8 KB (1,280 words) - 13:27, 9 August 2020
• XeTeX - Old Content
  ...tive TeX Processors]] | [[Fonts in XeTeX - Old Content]] | [[Encodings and Regimes in XeTeX]] > ...ns its strength in features by sacrificing TeX's usual cross-platformness, and some backwards compatibility.
  9 KB (1,472 words) - 08:28, 2 July 2022
• Aleph Guide
  [[Aleph]] is a typesetting engine derived from Omega and eTeX. Reasons for Aleph: # ConTeXt depends on the eTeX extensions, and even LaTeX now defaults to pdfeTeX.
  16 KB (2,235 words) - 08:28, 2 July 2022