Re: [LyX/master] Improve error message a bit more.
Am Dienstag, 1. Mai 2018 15:32:13 CEST schrieb Richard Heck : > > It would be handy if each switch would have own translation. Changing > > a dot anywhere, and you go crazy searching for the difference. > > > > That one is easy: It's just a single string, and it could just be split. > I suppose the > question is: Is it worth making work now for the translators by doing so > in order > possibly to save them work later? For 2.4 I think yes. ... > > > > This way, only the second phrase would have changed. > > > > In this case, too, it should be no problem, since we can just split the > string > into two parts, as in the attached. Same question whether it's worth it now. Also only for 2.4. Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] Group the switch of encoding for listings in utf8 documents
Am Dienstag, den 01.05.2018, 19:55 +0200 schrieb Enrico Forestieri:
> > - os << code << breakln << "\\end{lstlisting}\n";
> > + os << code << "\\end{lstlisting}\n";
> >}
>
> Jürgen, why this change? Here, breakln ensures that \end{lstlisting}
> is issued at the beginning of a line without introducing any blank
> line.
This change is by mistake (I wanted to copy but apparently cut).
I'll fix that. Thanks for the pointer.
Jürgen
signature.asc
Description: This is a digitally signed message part
Re: [LyX/master] Improve error message a bit more.
On 05/01/2018 02:38 PM, Kornel Benko wrote:
>
> Am Dienstag, 1. Mai 2018 13:55:56 CEST schrieb Richard Heck
> :
>
> > On 04/26/2018 01:43 AM, Kornel Benko wrote:
>
> > >
>
> > > Am Donnerstag, 26. April 2018 00:44:52 CEST schrieb Richard Kimberly
>
> > > Heck :
>
> > >
>
> > > > commit 821e10154739aa23191998b88a4bb7d9e0390628
>
> > >
>
> > > > Author: Richard Kimberly Heck
>
> > >
>
> > > > Date: Wed Apr 25 18:43:49 2018 -0400
>
> > >
>
> > > >
>
> > >
>
> > > > Improve error message a bit more.
>
> > >
>
> > > >
>
> > >
>
> > > > Sorry to Kornel, who had already updated sk.po!
>
> > >
>
> > >
>
> > >
>
> > > No problem. Sometimes I wish, some messages to translate were split
>
> > > into more parts.
>
> > >
>
> > > Like
>
> > >
>
> > > bformat(_("Part 1") + _("Part 2") + ... ), from_ascii(filePath(;
>
> > >
>
> > > Is that possible?
>
> > >
>
> > >
>
> > >
>
> > > On very long strings (see for instance the usage message) this would
>
> > > be handy.
>
> > >
>
> > >
>
> > >
>
> >
>
> > Can you explain how that would be handy? How would you want
>
> > to split it up in this case?
>
>
>
> Take for instance the help message.
>
> Command line switches (case sensitive):
>
> -help summarize LyX usage
>
> -userdir dir set user directory to dir
>
> -sysdir dir set system directory to dir
>
> -geometry WxH+X+Y set geometry of the main window
>
> -dbg feature[,feature]...
>
> select the features to debug.
>
> Type `lyx -dbg' to see the list of features
>
> -x [--execute] command
>
> where command is a lyx command.
>
> -e [--export] fmt
>
> where fmt is the export format of choice. Look in
>
> Tools->Preferences->File Handling->File Formats->Short Name
>
> to see which parameter (which differs from the format name
>
> in the File->Export menu) should be passed. To export to
>
> the document's default output format, use 'default'.
>
> Note that the order of -e and -x switches matters.
>
> -E [--export-to] fmt filename
>
> where fmt is the export format of choice (see --export),
>
> and filename is the destination filename.
>
> -i [--import] fmt file.xxx
>
> where fmt is the import format of choice
>
> and file.xxx is the file to be imported.
>
> -f [--force-overwrite] what
>
> where what is either `all', `main' or `none',
>
> specifying whether all files, main file only, or no files,
>
> respectively, are to be overwritten during a batch export.
>
> Anything else is equivalent to `all', but is not consumed.
>
> --ignore-error-message which
>
> allows you to ignore specific LaTeX error messages.
>
> Do not use for final documents! Currently supported values:
>
> * missing_glyphs: Fontspec `missing glyphs' error.
>
> -n [--no-remote]
>
> open documents in a new instance
>
> -r [--remote]
>
> open documents in an already running instance
>
> (a working lyxpipe is needed)
>
> -v [--verbose]
>
> report on terminal about spawned commands.
>
> -batch execute commands without launching GUI and exit.
>
> -version summarize version and build info
>
>
>
> It would be handy if each switch would have own translation. Changing
> a dot anywhere, and you go crazy searching for the difference.
>
That one is easy: It's just a single string, and it could just be split.
I suppose the
question is: Is it worth making work now for the translators by doing so
in order
possibly to save them work later?
> In your case,
>
> bformat(_("The directory path to the
> document\n%1$s\n"
>
> "contains spaces, but your TeX installation
> does "
>
> "not allow them. You should save the file
> to a directory "
>
> "whose name does not contain spaces."),
> from_ascii(filePath(;
>
> There are 2 phrases.
>
> The directory path to the document\n%1$s\n"
>
> "contains spaces, but your TeX installation
> does not allow them."
>
> and
>
> "You should save the file to a directory whose name does not contain
> spaces.
>
>
>
> This way, only the second phrase would have changed.
>
In this case, too, it should be no problem, since we can just split the
string
into two parts, as in the attached. Same question whether it's worth it now.
Riki
diff --git a/src/Buffer.cpp b/src/Buffer.cpp
index 043f0cc..5d3ded2 100644
--- a/src/Buffer.cpp
+++ b/src/Buffer.cpp
@@ -4365,8 +4365,9 @@ Buffer::ExportStatus Buffer::doExport(string const &
target, bool put_in_tempdir
Alert::error(_("File name error"),
bformat(_("The directory path to the document\n%1$s\n"
"contains spaces, but your TeX installation does "
- "not allow them. You should save the file to a
directory "
- "whose name does not contain spaces."),
from_ascii(filePath(;
+ "not allow them."), from_ascii(filePath())) +
+ _("You should save the file to a directory "
Re: [LyX/master] Improve error message a bit more.
Am Dienstag, 1. Mai 2018 13:55:56 CEST schrieb Richard Heck :
> On 04/26/2018 01:43 AM, Kornel Benko wrote:
> >
> > Am Donnerstag, 26. April 2018 00:44:52 CEST schrieb Richard Kimberly
> > Heck :
> >
> > > commit 821e10154739aa23191998b88a4bb7d9e0390628
> >
> > > Author: Richard Kimberly Heck
> >
> > > Date: Wed Apr 25 18:43:49 2018 -0400
> >
> > >
> >
> > > Improve error message a bit more.
> >
> > >
> >
> > > Sorry to Kornel, who had already updated sk.po!
> >
> >
> >
> > No problem. Sometimes I wish, some messages to translate were split
> > into more parts.
> >
> > Like
> >
> > bformat(_("Part 1") + _("Part 2") + ... ), from_ascii(filePath(;
> >
> > Is that possible?
> >
> >
> >
> > On very long strings (see for instance the usage message) this would
> > be handy.
> >
> >
> >
>
> Can you explain how that would be handy? How would you want
> to split it up in this case?
Take for instance the help message.
Command line switches (case sensitive):
-help summarize LyX usage
-userdir dir set user directory to dir
-sysdir dirset system directory to dir
-geometry WxH+X+Y set geometry of the main window
-dbg feature[,feature]...
select the features to debug.
Type `lyx -dbg' to see the list of features
-x [--execute] command
where command is a lyx command.
-e [--export] fmt
where fmt is the export format of choice. Look in
Tools->Preferences->File Handling->File Formats->Short Name
to see which parameter (which differs from the format name
in the File->Export menu) should be passed. To export to
the document's default output format, use 'default'.
Note that the order of -e and -x switches matters.
-E [--export-to] fmt filename
where fmt is the export format of choice (see --export),
and filename is the destination filename.
-i [--import] fmt file.xxx
where fmt is the import format of choice
and file.xxx is the file to be imported.
-f [--force-overwrite] what
where what is either `all', `main' or `none',
specifying whether all files, main file only, or no files,
respectively, are to be overwritten during a batch export.
Anything else is equivalent to `all', but is not consumed.
--ignore-error-message which
allows you to ignore specific LaTeX error messages.
Do not use for final documents! Currently supported values:
* missing_glyphs: Fontspec `missing glyphs' error.
-n [--no-remote]
open documents in a new instance
-r [--remote]
open documents in an already running instance
(a working lyxpipe is needed)
-v [--verbose]
report on terminal about spawned commands.
-batchexecute commands without launching GUI and exit.
-version summarize version and build info
It would be handy if each switch would have own translation. Changing a dot
anywhere, and you go crazy searching for the difference.
In your case,
bformat(_("The directory path to the document\n%1$s\n"
"contains spaces, but your TeX installation does "
"not allow them. You should save the file to a
directory "
"whose name does not contain spaces."),
from_ascii(filePath(;
There are 2 phrases.
The directory path to the document\n%1$s\n"
"contains spaces, but your TeX installation does not
allow them."
and
"You should save the file to a directory whose name does not contain
spaces.
This way, only the second phrase would have changed.
> Riki
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, 1. Mai 2018 19:16:26 CEST schrieb Jürgen Spitzmüller
:
> Am Dienstag, den 01.05.2018, 18:46 +0200 schrieb Kornel Benko:
> > > Hm, but how do you switch encoding with this?
> >
> > I don't understand.
> > The files to be compiled are copied to a test-directory. While the
> > are copied, the contend of some lines
> > is changed for example all references to other files are handled. And
> > so is also \inputencoding handled.
> > So, the only relevant change is this line before throwing it to lyx
> > for export.
> >
> > > > 1903 - DEFAULTOUTPUT_export/doc/ar/UserGuide_pdf4_systemF
> > (Failed)
>
> Yes, but with system fonts (as in 1903), changing \inputencoding does
> not matter, since in that case, there is always utf8 output (without
> inputenc).
Ouch. I just compared the two files, they are identical. Whats more, the change
will be done only
for TeX fonts.
Here the errors:
Finished processing index.
WARNING: Found no :close-range matching an already opened one!
Location-reference is 14 in keyword (ﺐﻴﺋﺎﺗ ﺎﻠﻔﻗﺭﺓ).
Maybe I lost some of the regular location-references.
WARNING: Found a :close-range in the index that wasn't opened before!
Location-reference is 27 in keyword (ﺐﻴﺋﺓ ﺎﻠﻔﻗﺭﺓ)
I'll continue and ignore this.
ERROR: Cross-reference-target ("Image formats}|hyperpage") does not exist!
ERROR: Cross-reference-target ("Image formats}|hyperpage") does not exist!
ERROR: Cross-reference-target ("Image formats}|hyperpage") does not exist!
ERROR: Cross-reference-target ("Image formats}|hyperpage") does not exist!
Writing markup... [10%] [20%] [30%] [40%] [50%] [60%] [70%] [80%] [90%] [100%]
Markup written into file "./UserGuide_pdf4_systemF.ind".
ERROR: Cross-reference-target ("Image formats}|hyperpage") does not exist!
...
So this has nothing to do with encoding.
Sigh!
> Jürgen
>
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: [LyX/master] Improve error message a bit more.
On 04/26/2018 01:43 AM, Kornel Benko wrote:
>
> Am Donnerstag, 26. April 2018 00:44:52 CEST schrieb Richard Kimberly
> Heck :
>
> > commit 821e10154739aa23191998b88a4bb7d9e0390628
>
> > Author: Richard Kimberly Heck
>
> > Date: Wed Apr 25 18:43:49 2018 -0400
>
> >
>
> > Improve error message a bit more.
>
> >
>
> > Sorry to Kornel, who had already updated sk.po!
>
>
>
> No problem. Sometimes I wish, some messages to translate were split
> into more parts.
>
> Like
>
> bformat(_("Part 1") + _("Part 2") + ... ), from_ascii(filePath(;
>
> Is that possible?
>
>
>
> On very long strings (see for instance the usage message) this would
> be handy.
>
>
>
Can you explain how that would be handy? How would you want
to split it up in this case?
Riki
signature.asc
Description: OpenPGP digital signature
Re: [LyX/master] Group the switch of encoding for listings in utf8 documents
On Tue, May 01, 2018 at 02:22:12PM +0200, Juergen Spitzmueller wrote:
> commit 2009469219dd81ec932f686eb9985829c426732a
> Author: Juergen Spitzmueller
> Date: Tue May 1 14:21:05 2018 +0200
>
> Group the switch of encoding for listings in utf8 documents
>
> Else, \cprotect'ed documents fail.
> ---
> src/insets/InsetListings.cpp | 11 ---
> src/output_latex.cpp |4 ++--
> src/output_latex.h |2 +-
> 3 files changed, 11 insertions(+), 6 deletions(-)
[...]
> @@ -332,12 +335,14 @@ void InsetListings::latex(otexstream & os, OutputParams
> const & runparams) const
> }
> os << from_utf8(param_string) << "]\n";
> }
> - os << code << breakln << "\\end{lstlisting}\n";
> + os << code << "\\end{lstlisting}\n";
> }
Jürgen, why this change? Here, breakln ensures that \end{lstlisting}
is issued at the beginning of a line without introducing any blank line.
--
Enrico
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, den 01.05.2018, 18:46 +0200 schrieb Kornel Benko: > > Hm, but how do you switch encoding with this? > > I don't understand. > The files to be compiled are copied to a test-directory. While the > are copied, the contend of some lines > is changed for example all references to other files are handled. And > so is also \inputencoding handled. > So, the only relevant change is this line before throwing it to lyx > for export. > > > > 1903 - DEFAULTOUTPUT_export/doc/ar/UserGuide_pdf4_systemF > (Failed) Yes, but with system fonts (as in 1903), changing \inputencoding does not matter, since in that case, there is always utf8 output (without inputenc). Jürgen signature.asc Description: This is a digitally signed message part
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, 1. Mai 2018 18:21:25 CEST schrieb Jürgen Spitzmüller : > Am Dienstag, den 01.05.2018, 16:17 +0200 schrieb Kornel Benko: > > Excluding Japanese, Hebrew(pdf3) and aa_sample, there is only left > > > > 1619 - export/doc/Math_dvi3_texF (Failed) > > 1626 - export/doc/Math_pdf5_texF (Failed) > > 1672 - export/doc/UserGuide_dvi3_texF (Failed) > > 1679 - export/doc/UserGuide_pdf5_texF (Failed) > > 1790 - export/doc/attic/id_UserGuide_dvi3_texF (Failed) > > 1797 - export/doc/attic/id_UserGuide_pdf5_texF (Failed) > > 2071 - export/doc/de/Math_dvi3_texF (Failed) > > 2078 - export/doc/de/Math_pdf5_texF (Failed) > > 2119 - export/doc/de/UserGuide_dvi3_texF (Failed) > > 2126 - export/doc/de/UserGuide_pdf5_texF (Failed) > > 2471 - export/doc/fr/Math_dvi3_texF (Failed) > > 2478 - export/doc/fr/Math_pdf5_texF (Failed) > > 2519 - export/doc/fr/UserGuide_dvi3_texF (Failed) > > 2526 - export/doc/fr/UserGuide_pdf5_texF (Failed) > > So these are all LuaTeX compilations with TeX font (i.e., luainputenc). > The errors seem to be font-dependent (I get less or more if I switch > fonts). > > Of course it would be nice to know what happens here, but OTOH LuaTeX > with utf8 normally means non-TeX fonts. So this is not a deal-breaker. > > > All of them compile with 'auto' selected. > > Hm, but how do you switch encoding with this? I don't understand. The files to be compiled are copied to a test-directory. While the are copied, the contend of some lines is changed for example all references to other files are handled. And so is also \inputencoding handled. So, the only relevant change is this line before throwing it to lyx for export. > > 1903 - DEFAULTOUTPUT_export/doc/ar/UserGuide_pdf4_systemF (Failed) > > Jürgen > Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, den 01.05.2018, 16:17 +0200 schrieb Kornel Benko: > Excluding Japanese, Hebrew(pdf3) and aa_sample, there is only left > > 1619 - export/doc/Math_dvi3_texF (Failed) > 1626 - export/doc/Math_pdf5_texF (Failed) > 1672 - export/doc/UserGuide_dvi3_texF (Failed) > 1679 - export/doc/UserGuide_pdf5_texF (Failed) > 1790 - export/doc/attic/id_UserGuide_dvi3_texF (Failed) > 1797 - export/doc/attic/id_UserGuide_pdf5_texF (Failed) > 2071 - export/doc/de/Math_dvi3_texF (Failed) > 2078 - export/doc/de/Math_pdf5_texF (Failed) > 2119 - export/doc/de/UserGuide_dvi3_texF (Failed) > 2126 - export/doc/de/UserGuide_pdf5_texF (Failed) > 2471 - export/doc/fr/Math_dvi3_texF (Failed) > 2478 - export/doc/fr/Math_pdf5_texF (Failed) > 2519 - export/doc/fr/UserGuide_dvi3_texF (Failed) > 2526 - export/doc/fr/UserGuide_pdf5_texF (Failed) So these are all LuaTeX compilations with TeX font (i.e., luainputenc). The errors seem to be font-dependent (I get less or more if I switch fonts). Of course it would be nice to know what happens here, but OTOH LuaTeX with utf8 normally means non-TeX fonts. So this is not a deal-breaker. > All of them compile with 'auto' selected. Hm, but how do you switch encoding with this? > 1903 - DEFAULTOUTPUT_export/doc/ar/UserGuide_pdf4_systemF (Failed) Jürgen > Kornel signature.asc Description: This is a digitally signed message part
Re: [LyX/master] Fix #10858 compiler warnings.
On 05/01/2018 11:27 AM, Scott Kostyshak wrote:
> On Sat, Dec 16, 2017 at 04:41:40AM +, Richard Heck wrote:
>> commit b954f478e31e640f292f865a5c41c65565e5c02a
>> Author: Richard Heck
>> Date: Fri Dec 15 23:41:32 2017 -0500
>>
>> Fix #10858 compiler warnings.
>> ---
>> src/mathed/InsetMathHull.cpp | 16 +++-
>> src/support/gzstream.cpp |2 +-
>> 2 files changed, 8 insertions(+), 10 deletions(-)
> A git bisect suggests that this caused the following change for me:
>
> When I export the attached .lyx file, I get the following message in the
> terminal:
>
> mathed/InsetMath.cpp (91): InsetMath::metricsT(Text) called directly!
>
> With the non-MWE that I originally saw this, I get that message repeated
> many times.
Hmm. The attached fixes it, and also explains a bit why it's happening.
JMarc?
Riki
diff --git a/src/mathed/InsetMathHull.cpp b/src/mathed/InsetMathHull.cpp
index 8398347..1da9363 100644
--- a/src/mathed/InsetMathHull.cpp
+++ b/src/mathed/InsetMathHull.cpp
@@ -2321,8 +2321,11 @@ bool InsetMathHull::readQuiet(Lexer & lex)
int InsetMathHull::plaintext(odocstringstream & os,
OutputParams const & op, size_t max_length) const
{
- // Try enabling this now that there is a flag as requested at #2275.
- if (buffer().isExporting() && display()) {
+ // We could put buffer().isExporting() here, as requested
+ // at #2275, but this ends up being called to construct the
+ // TOC during output, and that leads to the warning:
+ // mathed/InsetMath.cpp (91): InsetMath::metricsT(Text) called
directly!
+ if (0 && display()) {
Dimension dim;
TextMetricsInfo mi;
metricsT(mi, dim);
Re: [LyX/master] Fix #10858 compiler warnings.
On Sat, Dec 16, 2017 at 04:41:40AM +, Richard Heck wrote: > commit b954f478e31e640f292f865a5c41c65565e5c02a > Author: Richard Heck > Date: Fri Dec 15 23:41:32 2017 -0500 > > Fix #10858 compiler warnings. > --- > src/mathed/InsetMathHull.cpp | 16 +++- > src/support/gzstream.cpp |2 +- > 2 files changed, 8 insertions(+), 10 deletions(-) A git bisect suggests that this caused the following change for me: When I export the attached .lyx file, I get the following message in the terminal: mathed/InsetMath.cpp (91): InsetMath::metricsT(Text) called directly! With the non-MWE that I originally saw this, I get that message repeated many times. Scott mwe_terminal_message.23.lyx Description: application/lyx signature.asc Description: PGP signature
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, 1. Mai 2018 15:30:16 CEST schrieb Jürgen Spitzmüller : > Am Dienstag, den 01.05.2018, 15:15 +0200 schrieb Kornel Benko: > > All .*Customization_pdf2.* test pass. > > So what are the 89 failing cases you were talking about? > > Jürgen > Sorry, it is less now. Excluding Japanese, Hebrew(pdf3) and aa_sample, there is only left 1619 - export/doc/Math_dvi3_texF (Failed) 1626 - export/doc/Math_pdf5_texF (Failed) 1672 - export/doc/UserGuide_dvi3_texF (Failed) 1679 - export/doc/UserGuide_pdf5_texF (Failed) 1790 - export/doc/attic/id_UserGuide_dvi3_texF (Failed) 1797 - export/doc/attic/id_UserGuide_pdf5_texF (Failed) 1903 - DEFAULTOUTPUT_export/doc/ar/UserGuide_pdf4_systemF (Failed) 2071 - export/doc/de/Math_dvi3_texF (Failed) 2078 - export/doc/de/Math_pdf5_texF (Failed) 2119 - export/doc/de/UserGuide_dvi3_texF (Failed) 2126 - export/doc/de/UserGuide_pdf5_texF (Failed) 2471 - export/doc/fr/Math_dvi3_texF (Failed) 2478 - export/doc/fr/Math_pdf5_texF (Failed) 2519 - export/doc/fr/UserGuide_dvi3_texF (Failed) 2526 - export/doc/fr/UserGuide_pdf5_texF (Failed) All of them compile with 'auto' selected. Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, den 01.05.2018, 15:15 +0200 schrieb Kornel Benko: > All .*Customization_pdf2.* test pass. So what are the 89 failing cases you were talking about? Jürgen signature.asc Description: This is a digitally signed message part
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, den 01.05.2018, 15:15 +0200 schrieb Kornel Benko:
> export/doc/ja/Customization_(pdf|pdf3|dvi) fails (utf8|utf8x), passes
> by auto
> ...
> ) (/usr9/local/texlive/2017/texmf-
> dist/tex/platex/jsclasses/okumacro.sty
> ! LaTeX Error: This file needs format `pLaTeX2e'
> Desc: LaTeX Error: This file needs format `pLaTeX2e'
> Text: \NeedsTeXFormat{pLaTeX2e}
>
> The current input file will not be processed further,
> because it was written for some other flavor of TeX.
> You're in trouble here. Try typingto proceed.
> If that doesn't work, type X to quit.
You can exclude this test. Japanese requires a specific encoding, utf8
won't work. See https://www.lyx.org/trac/ticket/9065
Jürgen
signature.asc
Description: This is a digitally signed message part
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, 1. Mai 2018 14:23:04 CEST schrieb Jürgen Spitzmüller
:
> Am Montag, den 30.04.2018, 19:53 +0200 schrieb Kornel Benko:
> > pass now. Remaining are:
> > DEFAULTOUTPUT_export/doc/Customization_pdf2
> > DEFAULTOUTPUT_export/doc/es/Customization_pdf2
> > DEFAULTOUTPUT_export/doc/fr/Customization_pdf2
>
> This should compile now as well. So all from this list done.
Nice.
All .*Customization_pdf2.* test pass.
export/doc/ja/Customization_(pdf|pdf3|dvi) fails (utf8|utf8x), passes by auto
...
) (/usr9/local/texlive/2017/texmf-dist/tex/platex/jsclasses/okumacro.sty
! LaTeX Error: This file needs format `pLaTeX2e'
Desc: LaTeX Error: This file needs format `pLaTeX2e'
Text: \NeedsTeXFormat{pLaTeX2e}
The current input file will not be processed further,
because it was written for some other flavor of TeX.
You're in trouble here. Try typingto proceed.
If that doesn't work, type X to quit.
> Jürgen
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Montag, den 30.04.2018, 19:53 +0200 schrieb Kornel Benko: > pass now. Remaining are: > DEFAULTOUTPUT_export/doc/Customization_pdf2 > DEFAULTOUTPUT_export/doc/es/Customization_pdf2 > DEFAULTOUTPUT_export/doc/fr/Customization_pdf2 This should compile now as well. So all from this list done. Jürgen signature.asc Description: This is a digitally signed message part
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, den 01.05.2018, 13:58 +0200 schrieb Kornel Benko: > OK, but even then, there are at least 89 fails. Ant that is the bad > news. So the list increased after my recent commits? You listed far less files. Jürgen > > > Jürgen > > > Kornel > > signature.asc Description: This is a digitally signed message part
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, 1. Mai 2018 13:18:53 CEST schrieb Jürgen Spitzmüller : > Am Dienstag, den 01.05.2018, 11:25 +0200 schrieb Kornel Benko: > > The bad news is, that neither 'utf8' nor 'utf8x' can replace the > > 'auto' inputencoding. > > You must use utf8x only for Hebrew, utf8 for all the others. OK, but even then, there are at least 89 fails. Ant that is the bad news. > Jürgen > Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, den 01.05.2018, 11:25 +0200 schrieb Kornel Benko: > The bad news is, that neither 'utf8' nor 'utf8x' can replace the > 'auto' inputencoding. You must use utf8x only for Hebrew, utf8 for all the others. Jürgen > > Kornel > > signature.asc Description: This is a digitally signed message part
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, 1. Mai 2018 09:20:36 CEST schrieb Kornel Benko : > Am Dienstag, 1. Mai 2018 08:19:37 CEST schrieb Jürgen Spitzmüller > : > > Am Montag, den 30.04.2018, 19:53 +0200 schrieb Kornel Benko: > > > DEFAULTOUTPUT_export/doc/de/EmbeddedObjects_pdf2 > > > > Should work now. > > > > > export/examples/aa_sample_pdf2 > > > > You can exclude this from the test. The class loads inputenc itself, > > and the encoding is specified via class option (currently "latin9"; > > changing that to "utf8" makes the document compile with utf8). > > > > Jürgen > > OK. > Now the bad news. Trying to use 'utf8x' instead of 'auto' on all relevant exports led to 134 failed tests. Trying to use 'utf8' instead of 'auto' on the previously failed, led to 89 failed tests. Without change, e.g. 'auto' -> 'auto', on these tests I have only 6 failed left. 1903:DEFAULTOUTPUT_export/doc/ar/UserGuide_pdf4_systemF 2571:export/doc/he/Intro_pdf3 2587:export/doc/he/Tutorial_pdf3 5239:export/examples/he/example_lyxified_pdf3 5255:export/examples/he/example_raw_pdf3 5271:export/examples/he/splash_pdf3 The pdf3 tests fail because dvipdfmx failes to find (or create) the virtual font. kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 DavidCLM-Medium.pfa mktexpk: don't know how to create bitmap font for DavidCLM-Medium.pfa. mktexpk: perhaps DavidCLM-Medium.pfa is missing from the map file. kpathsea: Appending font creation commands to missfont.log. dvipdfmx:warning: Could not locate a virtual/physical font for TFM "david". dvipdfmx:warning: >> This font is mapped to a physical font "DavidCLM-Medium.pfa". dvipdfmx:warning: >> Please check if kpathsea library can find this font: DavidCLM-Medium.pfa dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF output... The bad news is, that neither 'utf8' nor 'utf8x' can replace the 'auto' inputencoding. Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] unicodesymbols: add general way to require a feature only for specific encodings
Am Dienstag, 1. Mai 2018 08:19:37 CEST schrieb Jürgen Spitzmüller : > Am Montag, den 30.04.2018, 19:53 +0200 schrieb Kornel Benko: > > DEFAULTOUTPUT_export/doc/de/EmbeddedObjects_pdf2 > > Should work now. > > > export/examples/aa_sample_pdf2 > > You can exclude this from the test. The class loads inputenc itself, > and the encoding is specified via class option (currently "latin9"; > changing that to "utf8" makes the document compile with utf8). > > Jürgen OK. Kornel signature.asc Description: This is a digitally signed message part.
