anne/lyx_mirror
1
0
Fork 0
mirror of https://git.lyx.org/repos/lyx.git synced 2024-11-28 20:45:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
27ba6f282d
lyx_mirror/autotests/export/latex/inputenc-utf8-plain.lyx

142 lines
3.1 KiB
Plaintext
Raw Normal View History

ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
#LyX 2.4 created this file. For more info see https://www.lyx.org/
ctest update: Japanese documents (should) work with non-TeX fonts. * do not ignore Japanese (platex) with system fonts. * CJK can be used with XeTeX and TeX-fonts if the input encoding is utf8. do not ignore. * TODO: set non-TeX fonts and uninvert where possible.
2019-04-12 08:03:44 +00:00
\lyxformat 572
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
\begin_preamble
\@ifpackageloaded{fontspec}{%
% Unicode fonts, nothing to do
}{% setup Unicode with 8-bit LaTeX fonts:
% character-providing packages are not auto-loaded with "utf8-plain"
\usepackage{textcomp}
\ifdefined\XeTeXinputencoding
% XeTeX in legacy mode
\XeTeXinputencoding "bytes" % current file
\XeTeXdefaultencoding "bytes" % included files
\let\origUmathchar\Umathchar
\let\Umathchar\@undefined
\usepackage[utf8]{inputenc}
\let\Umathchar\origUmathchar
\fi
\ifdefined\directlua
\usepackage[utf8]{luainputenc} % must come after textcomp!
\else
\usepackage[utf8]{inputenc} % default since TeXLive 2018
\fi
% set up macro for INFINITY Character '∞'
\DeclareUnicodeCharacter{221E}{\ensuremath{\infty}}
}
\end_preamble
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\use_default_options true
\begin_modules
logicalmkup
\end_modules
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding utf8-plain
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
\fontencoding auto
\font_roman "lmodern" "default"
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\use_microtype false
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
\use_dash_ligatures false
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\graphics default
ctest update: Japanese documents (should) work with non-TeX fonts. * do not ignore Japanese (platex) with system fonts. * CJK can be used with XeTeX and TeX-fonts if the input encoding is utf8. do not ignore. * TODO: set non-TeX fonts and uninvert where possible.
2019-04-12 08:03:44 +00:00
\default_output_format pdf2
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\output_sync 0
\bibtex_command default
\index_command default
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
\float_placement class
\float_alignment class
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
\use_minted 0
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
\is_math_indent 0
\math_numbering_side default
\quotes_style english
\dynamic_quotes 0
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\papercolumns 1
\papersides 1
\paperpagestyle default
ctest update: Japanese documents (should) work with non-TeX fonts. * do not ignore Japanese (platex) with system fonts. * CJK can be used with XeTeX and TeX-fonts if the input encoding is utf8. do not ignore. * TODO: set non-TeX fonts and uninvert where possible.
2019-04-12 08:03:44 +00:00
\tablestyle default
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Standard
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
With LaTeX input encoding
\family typewriter
utf8-plain
\family default
(UTF-8 (XeTeX)), the author must ensure non-standard characters are defined
in the user preamble (see Document>Settings>LaTeX
\begin_inset space ~
\end_inset
Preamble).
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\end_layout
ctests: utf8-plain now works with all export variants. utf8-plain (Unicode (utf8 XeTeX)) is a power-user setting for the input encoding with two use cases: a) setup of system fonts or b) setup of input encoding supportuser preamble in the document class or user preamble. The test file is an example for use case b.
2019-01-07 22:17:47 +00:00
\begin_layout Itemize
Hübner und Örtel sind 30 µm groß.
\end_layout
\begin_layout Itemize
em- and en-dash: — –
\end_layout
\begin_layout Itemize
Textcomp characters: ¹²³¼½¬¸@ł€¶←→
\end_layout
\begin_layout Itemize
INFINITY Character defined in the user preamble: ∞
fix #10199 Non-encodable characters with XeTeX and utf8-plain XeTeX with TeX fonts is only safe with ASCII input encoding (see #9740) and we therefore force "ascii" when exporting with XeTeX and 8-bit TeX-fonts. However, "utf8-plain" is a "power-user" option, which allows to switch off LyX's encoding of the LaTeX file: keep this also for "XeTeX with TeX fonts". The user is responsible to ensure all characters can be processed and are correctly shown in the output. The provided test sample shows the problems with this encoding without special measures (like loading fontspec in the user-preamble or a document class).
2016-06-11 11:54:33 +00:00
\end_layout
\end_body
\end_document
Reference in New Issue Copy Permalink