Re: New export errors with TL19
Am Freitag, den 13.12.2019, 22:49 + schrieb Guenter Milde: > > > > > What error do you get? This compiles for me. > > Sure? It should be impossible: XeTeX export is disabled with TeX > fonts > and "inputencoding" legacy-default. You're right. I misread the suffixes. I agree with you that this test setting does not make sense. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Export Errors
I can't follow that thread. Is any of it relevant to the 2.3.x branch? Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
On 2019-12-13, Jürgen Spitzmüller wrote: > [-- Type: text/plain, Encoding: quoted-printable --] > Am Freitag, den 13.12.2019, 16:07 + schrieb Guenter Milde: >> On 2019-12-12, Jürgen Spitzmüller wrote: >> > [-- Type: text/plain, Encoding: quoted-printable --] >> > Am Donnerstag, den 12.12.2019, 13:45 +0100 schrieb Kornel Benko: >> > > Attached. >> > > export/export/latex/languages/th-en_utf8_pdf4_systemF >> > There is no proper typewriter font set. >> The document compiles fine here with the TLWG-Mono font. >> What error do you get? > I don't have this font installed. So LaTeX complains about missing Thai > in lm mono. >> > I don't have a typewriter font that includes Thai and Latin, but >> > setting Norasi (the Roman thai font used in the doc) fixes the >> > issue. >> The TLWG-Mono font set in this document supports both Latin and Thai. >> It is available in Debian in the package tlwg-mono-otf. > On OpenSuse, it's only available in a texlive package, but I have > blocked texlive. The site https://fontinfo.opensuse.org/fonts/TlwgMonoMedium.html points to the source ftp://linux.thai.net/pub/thailinux/software/fonts-tlwg/ which offers a set of tar archives with the tlwg fonts. Günter -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
On 2019-12-13, Kornel Benko wrote: > [-- Type: text/plain, Encoding: quoted-printable --] > Am Fri, 13 Dec 2019 16:34:25 +0100 > schrieb Jürgen Spitzmüller : >> Am Fr., 13. Dez. 2019 um 13:23 Uhr schrieb Kornel Benko : >> > > > >> > export/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex_pdf4_texF >> > > > >> > > >> > > What error do you get? This compiles for me. Sure? It should be impossible: XeTeX export is disabled with TeX fonts and "inputencoding" legacy-default. >> > Manual compilation is OK, in test env it fails >> > >> > The reason is the sequence of setting for pdf4_texF format >> > To verify, try following: >> > 1.) open the file >> > autotests/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex.lyx >> > 2.) deselect non-tex fonts Now, input encoding is legacy-default, the toolbar button "View PDF (XeTeX)" is grey (and inactive), File>Export no longer contains "PDF (XeTeX)" and Document>Settings>Formats>Default output format changed to "Default". >> > 3.) save the file >> > 4.) open the file try to select output format to pdf(xetex) >> > not possible !!! >> > 5.) select tex-fonts I suppose you meant select "non-TeX fonts"? >> > 6.) select output format to pdf(xetex) >> > 7.) de-select non-tex fonts Now, again: input encoding is legacy-default, the toolbar button "View PDF (XeTeX)" is grey (and inactive), File>Export no longer contains "PDF (XeTeX)" and Document>Settings>Formats>Default output format changed to "Default". >> > 8.) compilation OK Maybe you started the compilation with the "View" or "Update" button? As the default output changed to "Default", this works but does not use XeTeX. >> So is this a problem in the test design are a bug a real user can encounter? A real user will just realize that she cannot compile the document with XeTeX (the toolbar button is grey). The problem in the test design is, that in order to maximize the test coverage with the existing sample documents, every document is tested with all export formats supported by LyX unless manually excluded. As no standard documentation document supports XeTeX with TeX-fonts, it would be more clean to drop the auto-creation of "pdf4_texF" tests from documents with "\use_non_tex_fonts true". OTOH, the XeTeX specific "swapped columns" problem documented in wrong_output_3059-rtl-tables-xetex.lyx is solved (thank you, Jürgen). We may remove the this document. (Mind, that 3059-language-in-tables.lyx still fails because #3059 is not solved.) Thanks, Günter -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
On 2019-12-13, Kornel Benko wrote: >> > > > export/examples/ko/cjk-ko-doc_pdf4_systemF >> > > > >> > > This works for me. >> > >> > I get >> > Missing character: There is no ⅺ in font NanumGothic/OT:mapping=tex-text;! >> > Missing character: There is no ⅻ in font NanumGothic/OT:mapping=tex-text;! >> > Missing character: There is no Ⅺ in font NanumGothic/OT:mapping=tex-text;! >> > Missing character: There is no Ⅻ in font NanumGothic/OT:mapping=tex-text;! >> > >> A font problem at your end? > Looks like that. But I am unsure, what to do. The strange thing is, that NanumGothic is not called (at least not directly) and not used in the output (at least here). I do not have NanumGothic non-TeX fonts installed but all 15 "cjk-ko-doc" tests pass. NanumGothic is a fallback/default font setting, however, with non-TeX fonts it is overridden by the combination of GUI font selection and LaTeX preamble code. OTOH, a lot of "nanum*" fonts are used with pdflatex/TeX-fonts. Do you have the UnJamoBatang, UnJamoNovel, and UnTaza fonts installed? Are they used in the PDF (XeTeX) output. Günter -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
On Fri, Dec 13, 2019 at 06:57:56PM +0100, Jürgen Spitzmüller wrote: > Am Donnerstag, den 12.12.2019, 15:51 -0500 schrieb Scott Kostyshak: > > I would be interested in working on the documentation. The more > > specific ideas you have (like re-testing the failed tests), the > > easier > > it will be for me to improve the documentation. > > I don't have specific ideas. I was just trying to run the tests and > felt quite lost in general. OK. It is indeed complicated. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Donnerstag, den 12.12.2019, 15:51 -0500 schrieb Scott Kostyshak: > I would be interested in working on the documentation. The more > specific ideas you have (like re-testing the failed tests), the > easier > it will be for me to improve the documentation. I don't have specific ideas. I was just trying to run the tests and felt quite lost in general. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Freitag, den 13.12.2019, 16:29 + schrieb Guenter Milde: > It compiles fine here with FreeSerif Version 0412.2263 from the > "fonts-freefont-otf" package version 20120503-9. I have FreeSerif 1.548, downloaded from somewhere on the Interweb. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Freitag, den 13.12.2019, 16:07 + schrieb Guenter Milde: > On 2019-12-12, Jürgen Spitzmüller wrote: > > > [-- Type: text/plain, Encoding: quoted-printable --] > > Am Donnerstag, den 12.12.2019, 13:45 +0100 schrieb Kornel Benko: > > > Attached. > > > export/export/latex/languages/th-en_utf8_pdf4_systemF > > There is no proper typewriter font set. > > The document compiles fine here with the TLWG-Mono font. > What error do you get? I don't have this font installed. So LaTeX complains about missing Thai in lm mono. > > > I don't have a typewriter font that includes Thai and Latin, but > > setting Norasi (the Roman thai font used in the doc) fixes the > > issue. > > The TLWG-Mono font set in this document supports both Latin and Thai. > It is available in Debian in the package tlwg-mono-otf. On OpenSuse, it's only available in a texlive package, but I have blocked texlive. Jürgen > > Günter > signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Fri, 13 Dec 2019 16:34:25 +0100 schrieb Jürgen Spitzmüller : > Am Fr., 13. Dez. 2019 um 13:23 Uhr schrieb Kornel Benko : > > > > > > > export/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex_pdf4_texF > > > > > > > > > > What error do you get? This compiles for me. > > > > Manual compilation is OK, in test env it fails > > > > The reason is the sequence of setting for pdf4_texF format > > To verify, try following: > > 1.) open the file > > autotests/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex.lyx > > 2.) deselect non-tex fonts > > 3.) save the file > > 4.) open the file try to select output format to pdf(xetex) > > not possible !!! > > 5.) select tex-fonts > > 6.) select output format to pdf(xetex) > > 7.) de-select non-tex fonts > > 8.) compilation OK > > > > So is this a problem in the test design are a bug a real user can encounter? > > > > > > export/examples/ko/cjk-ko-doc_pdf4_systemF > > > > > > > This works for me. > > > > I get > > Missing character: There is no ⅺ in font NanumGothic/OT:mapping=tex-text;! > > Missing character: There is no ⅻ in font NanumGothic/OT:mapping=tex-text;! > > Missing character: There is no Ⅺ in font NanumGothic/OT:mapping=tex-text;! > > Missing character: There is no Ⅻ in font NanumGothic/OT:mapping=tex-text;! > > > > A font problem at your end? > > Jürgen Looks like that. But I am unsure, what to do. Kornel pgpMPXfKatglh.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Fri, 13 Dec 2019 16:23:32 +0100 schrieb Jürgen Spitzmüller : > Am Fr., 13. Dez. 2019 um 13:23 Uhr schrieb Kornel Benko : > > > But I was using the polyglossia-master. > > > > I meant: Now fixed in polyglossia master (after your report). > > Jürgen OK, export/examples/sk/Welcome_pdf4_systemF with success now. Kornel pgpISJWUwN320.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
On 2019-12-12, Jürgen Spitzmüller wrote:
> As to export/export/latex/languages/supported-languages_pdf4_systemF
> and maybe others, I get an error due to missing glyphs.
Which?
It compiles fine here with FreeSerif Version 0412.2263 from the
"fonts-freefont-otf" package version 20120503-9.
> The following preamble setting helps:
> \AtBeginDocument{
> \@ifpackageloaded{fontspec}{%
> \newfontfamily\arabicfont[Script=Arabic]{Amiri}%
> }{}
> }
Should not be required, the log says_
Package fontspec Info: Font family 'FreeSerif(1)' created for font 'FreeSerif'
(fontspec) with options
(fontspec) [Ligatures=TeX,Mapping=tex-text,Script=Arabic].
...
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
On 2019-12-12, Jürgen Spitzmüller wrote: > [-- Type: text/plain, Encoding: quoted-printable --] > Am Donnerstag, den 12.12.2019, 13:45 +0100 schrieb Kornel Benko: >> Attached. >> export/export/latex/languages/th-en_utf8_pdf4_systemF > There is no proper typewriter font set. The document compiles fine here with the TLWG-Mono font. What error do you get? > I don't have a typewriter font that includes Thai and Latin, but > setting Norasi (the Roman thai font used in the doc) fixes the issue. The TLWG-Mono font set in this document supports both Latin and Thai. It is available in Debian in the package tlwg-mono-otf. Günter -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Fr., 13. Dez. 2019 um 13:23 Uhr schrieb Kornel Benko : > > > > export/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex_pdf4_texF > > > > > > > What error do you get? This compiles for me. > > Manual compilation is OK, in test env it fails > > The reason is the sequence of setting for pdf4_texF format > To verify, try following: > 1.) open the file > autotests/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex.lyx > 2.) deselect non-tex fonts > 3.) save the file > 4.) open the file try to select output format to pdf(xetex) > not possible !!! > 5.) select tex-fonts > 6.) select output format to pdf(xetex) > 7.) de-select non-tex fonts > 8.) compilation OK > So is this a problem in the test design are a bug a real user can encounter? > > > export/examples/ko/cjk-ko-doc_pdf4_systemF > > > > > This works for me. > > I get > Missing character: There is no ⅺ in font NanumGothic/OT:mapping=tex-text;! > Missing character: There is no ⅻ in font NanumGothic/OT:mapping=tex-text;! > Missing character: There is no Ⅺ in font NanumGothic/OT:mapping=tex-text;! > Missing character: There is no Ⅻ in font NanumGothic/OT:mapping=tex-text;! > A font problem at your end? Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Fr., 13. Dez. 2019 um 13:23 Uhr schrieb Kornel Benko : > But I was using the polyglossia-master. > I meant: Now fixed in polyglossia master (after your report). Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Fri, 13 Dec 2019 12:03:09 +0100
schrieb Jürgen Spitzmüller :
> Am Fr., 13. Dez. 2019 um 10:52 Uhr schrieb Kornel Benko :
>
> > Same as before. ( + export/examples/sk/Welcome_pdf4_systemF)
> >
> This was a polyglossia bug. Fixes in polyglossia-master.
But I was using the polyglossia-master.
LaTeX.cpp (742): Log line: Package polyglossia Info: Option: english
variant=british.
LaTeX.cpp (742): Log line: Package polyglossia Info: Option: english
variant=british.
LaTeX.cpp (742): Log line: LaTeX Info: Redefining \rmfamily on input line 55.
LaTeX.cpp (742): Log line: LaTeX Info: Redefining \sffamily on input line 55.
LaTeX.cpp (742): Log line: LaTeX Info: Redefining \ttfamily on input line 55.
LaTeX.cpp (742): Log line: ! Bad character code (-1).
LaTeX.cpp (973): line: 60
Desc: Bad character code (-1).
Text: ... jazyka “\texttt{texlive-lang-czechslovak}
”.\\
A Unicode scalar value must be between 0 and "10.
I changed this one to zero.
LaTeX.cpp (742): Log line: Missing character: There is no ^^@ in font DejaVu
Sans
Mono/OT:script=latn;lang LaTeX.cpp (742): Log line: uage=DFLT;!
LaTeX.cpp (742): Log line: ! Bad character code (-1).
LaTeX.cpp (973): line: 60
Desc: Bad character code (-1).
Text: ... jazyka “\texttt{texlive-lang-czechslovak}
”.\\
A Unicode scalar value must be between 0 and "10.
I changed this one to zero.
> > export/export/latex/languages/th-en_utf8_pdf4_systemF
> >
>
> As said, missing Thai typewriter font.
>
OK
> > export/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex_pdf4_texF
> >
>
> What error do you get? This compiles for me.
Manual compilation is OK, in test env it fails
The reason is the sequence of setting for pdf4_texF format
To verify, try following:
1.) open the file
autotests/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex.lyx
2.) deselect non-tex fonts
3.) save the file
4.) open the file try to select output format to pdf(xetex)
not possible !!!
5.) select tex-fonts
6.) select output format to pdf(xetex)
7.) de-select non-tex fonts
8.) compilation OK
In test environment the setting in lyx-file is for tex-fonts and we try to
export to pdf4.
> > export/examples/Presentations/Foils_pdf4_systemF
> > export/examples/Presentations/Foils_pdf5_systemF
>
> export/examples/fr/Presentations/Foils_pdf4_systemF
>
> export/examples/fr/Presentations/Foils_pdf5_systemF
> >
>
> I'd say revert this, as long as we do not have a more clever automatism for
> graphic drivers.
>
I let it to Günter
> > export/examples/fr/Modules/Braille_dvi3_systemF
> > export/examples/fr/Modules/Braille_pdf4_systemF
> > export/examples/fr/Modules/Braille_pdf5_systemF
> >
> I've now replaced the hack that caused this by something more portable.
>
Confirmed
> > export/examples/ko/cjk-ko-doc_pdf4_systemF
> >
> This works for me.
I get
Missing character: There is no ⅺ in font NanumGothic/OT:mapping=tex-text;!
Missing character: There is no ⅻ in font NanumGothic/OT:mapping=tex-text;!
Missing character: There is no Ⅺ in font NanumGothic/OT:mapping=tex-text;!
Missing character: There is no Ⅻ in font NanumGothic/OT:mapping=tex-text;!
>
> Jürgen
>
Kornel
pgpFX2siiQbts.pgp
Description: Digitale Signatur von OpenPGP
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Fr., 13. Dez. 2019 um 10:52 Uhr schrieb Kornel Benko : > Same as before. ( + export/examples/sk/Welcome_pdf4_systemF) > This was a polyglossia bug. Fixes in polyglossia-master. > export/export/latex/languages/th-en_utf8_pdf4_systemF > As said, missing Thai typewriter font. > export/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex_pdf4_texF > What error do you get? This compiles for me. > export/examples/Presentations/Foils_pdf4_systemF > export/examples/Presentations/Foils_pdf5_systemF export/examples/fr/Presentations/Foils_pdf4_systemF export/examples/fr/Presentations/Foils_pdf5_systemF > I'd say revert this, as long as we do not have a more clever automatism for graphic drivers. > export/examples/fr/Modules/Braille_dvi3_systemF > export/examples/fr/Modules/Braille_pdf4_systemF > export/examples/fr/Modules/Braille_pdf5_systemF > I've now replaced the hack that caused this by something more portable. > export/examples/ko/cjk-ko-doc_pdf4_systemF > This works for me. Jürgen > export/examples/sk/Welcome_pdf4_systemF > > Kornel > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel > -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Fri, 13 Dec 2019 09:56:22 +0100 schrieb Jürgen Spitzmüller : > Am Do., 12. Dez. 2019 um 19:56 Uhr schrieb Kornel Benko : > > > OK now only 29 remaining tests are failing. > > From these 18 are failing because of aastex6.2. > > > > and the other 11? > > Jürgen Same as before. ( + export/examples/sk/Welcome_pdf4_systemF) export/export/latex/languages/th-en_utf8_pdf4_systemF export/export/latex/lyxbugs/wrong_output_3059-rtl-tables-xetex_pdf4_texF export/examples/Presentations/Foils_pdf4_systemF export/examples/Presentations/Foils_pdf5_systemF export/examples/fr/Modules/Braille_dvi3_systemF export/examples/fr/Modules/Braille_pdf4_systemF export/examples/fr/Modules/Braille_pdf5_systemF export/examples/fr/Presentations/Foils_pdf4_systemF export/examples/fr/Presentations/Foils_pdf5_systemF export/examples/ko/cjk-ko-doc_pdf4_systemF export/examples/sk/Welcome_pdf4_systemF Kornel pgp2VI_AGrzmX.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
Am Do., 12. Dez. 2019 um 19:56 Uhr schrieb Kornel Benko : > OK now only 29 remaining tests are failing. > From these 18 are failing because of aastex6.2. > and the other 11? Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: New export errors with TL19
On 2019-12-12, Jürgen Spitzmüller wrote: > Am Donnerstag, den 12.12.2019, 12:39 + schrieb Guenter Milde: >> In this case, please create also a minimal example of the failing >> document in the "dedicated latex export tests" directory (we should >> not >> expect users to add such preamble code to get working documents). > Why not? If you deal with multiple scripts, you need to setup proper > fonts. There's no way around that. Your are right. (This is Ticket #11522.) I gave the generic advice¹ without considering that * in this case, the affected document is already a "dedicated LaTeX export test" and * there is already a ticket dedicated to this problem. Sorry for the noise, Günter ¹ When the tests reveal a problem with one of our documentation files and there is a simple workaround: * Make the documentation file robust by adding the workaround, * create a minimal example document for the problem in "autotests/export/latex/", and * invert it in invertedTests. -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
