Re: lyx file from 2015 not converted to pdf
On 2020-03-19, Richard Kimberly Heck wrote: > On 3/19/20 12:20 PM, Paul A. Rubin wrote: >> On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: >>> I am trying to export from a lyx file produced in 2015 a pdf file, >>> but get this error: ... >>> further errors: >>> Error 84 returned from iconv when converting from UCS-4LE to >>> ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder >>> Wide-Zeichen This seems to indicate that there is an invalid utf8 multi-byte character somewhere in the *.lyx file. >>> How should I proceed? >> The last message (error 84) suggests that there may be a problem with >> character encoding. If it is in a preview snipped, that could explain >> the preceding message. >> You can try to isolate the problematic portion of the document by >> bisection. Once you know where the problem is, we may be able to offer >> more specific advise. > It's weird that you'd see the problem now and not in 2015. As Paul > suggests, this is a problem with one of the characters in the document: > We're trying to convert it to the right encoding and that's failing. > LyX should not crash when that happens, but sometimes it does. It may be due to a lyx2lyx problem, some mistake when converting the document from an old lyx format to the current one. Keep the original file, and from a copy remove parts until it compiles. Günter -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On 3/19/20 12:20 PM, Paul A. Rubin wrote: > On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: >> I am trying to export from a lyx file produced in 2015 a pdf file, >> but get this error: >> >> Error: Softwareausnahme erkannt >> >> LyX hat einen Fehler (Exception) entdeckt. Das Programm wird jetzt >> versuchen, alle ungespeicherten Dateien zu speichern, und dann beendet. >> >> Exception: std::exception >> Buffer.cpp (1601): >> /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL--NN.lyx.emergency >> Buffer.cpp (1601): >> /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL-NN.lyx.emergency >> Abgebrochen >> >> what might this mean > Exception: std::exception ?? >> >> I started the lyx on a terminal and there it starts with >> >> $ lyx PBR-FINAL--NN.lyx >> kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen." >> Warning: Failed to produce 1 preview snippet(s) >> QXcbClipboard: SelectionRequest too old >> >> further errors: >> Error 84 returned from iconv when converting from UCS-4LE to >> ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder >> Wide-Zeichen >> >> How should I proceed? >> Wolfgang > The last message (error 84) suggests that there may be a problem with > character encoding. If it is in a preview snipped, that could explain > the preceding message. > > You can try to isolate the problematic portion of the document by > bisection. Once you know where the problem is, we may be able to offer > more specific advise. It's weird that you'd see the problem now and not in 2015. As Paul suggests, this is a problem with one of the characters in the document: We're trying to convert it to the right encoding and that's failing. LyX should not crash when that happens, but sometimes it does. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: I am trying to export from a lyx file produced in 2015 a pdf file, but get this error: Error: Softwareausnahme erkannt LyX hat einen Fehler (Exception) entdeckt. Das Programm wird jetzt versuchen, alle ungespeicherten Dateien zu speichern, und dann beendet. Exception: std::exception Buffer.cpp (1601): /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL--NN.lyx.emergency Buffer.cpp (1601): /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL-NN.lyx.emergency Abgebrochen what might this mean > Exception: std::exception ?? I started the lyx on a terminal and there it starts with $ lyx PBR-FINAL--NN.lyx kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen." Warning: Failed to produce 1 preview snippet(s) QXcbClipboard: SelectionRequest too old further errors: Error 84 returned from iconv when converting from UCS-4LE to ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder Wide-Zeichen How should I proceed? Wolfgang The last message (error 84) suggests that there may be a problem with character encoding. If it is in a preview snipped, that could explain the preceding message. You can try to isolate the problematic portion of the document by bisection. Once you know where the problem is, we may be able to offer more specific advise. Paul -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
lyx file from 2015 not converted to pdf
I am trying to export from a lyx file produced in 2015 a pdf file, but get this error: Error: Softwareausnahme erkannt LyX hat einen Fehler (Exception) entdeckt. Das Programm wird jetzt versuchen, alle ungespeicherten Dateien zu speichern, und dann beendet. Exception: std::exception Buffer.cpp (1601): /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL--NN.lyx.emergency Buffer.cpp (1601): /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL-NN.lyx.emergency Abgebrochen what might this mean > Exception: std::exception ?? I started the lyx on a terminal and there it starts with $ lyx PBR-FINAL--NN.lyx kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen." Warning: Failed to produce 1 preview snippet(s) QXcbClipboard: SelectionRequest too old further errors: Error 84 returned from iconv when converting from UCS-4LE to ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder Wide-Zeichen How should I proceed? Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 2020-03-19 14:42, Richard Kimberly Heck wrote:
On 3/19/20 3:01 AM, Daniel wrote:
On 2020-03-18 14:59, Steve Hnizdur wrote:
Hi
When "Use Hyperref Support" is checked in PDF properties Lyx
automatically inserts
\usepackage[unicode=true,
bookmarks=false,
breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
{hyperref}
in the preamble. Any ideas where all these options come from? are
they hard coded?
Setting "unicode=false" in additional options doesn't seem to
override the "unicode=true". So if unicode=true is causing a problem
(in particular trying to redefine \C or \G) then this all has to
added manually.
MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
Hi
Yes, these options come from settings in the Hyperref dialog.
"bookmarks=..." = "Generate bookmars (toc)"
"breaklinks=..." = "Break links over lines"
"pdfborder=..." = "No frames around links"
"colorlinks=..." = "Color links"
"backref=..." = "Backreferences"
However, there seems to be no option for the "unicode=..." which seems
like an oversight. And the biggest problem is that according to the
manual:
Note however that some options (for example unicode) can only be used
as packge options,and not in \hypersetup as the option settings are
processed as the package is read. (p. 6)
So, unicode=false has no effect as an additional option.
My guess is that this is a bug in LyX but others might know better.
Well, the code is:
// Since LyX uses unicode, also set the PDF strings to unicode strings
// with the hyperref option "unicode". (With Xe/LuaTeX and pTeX,
// unicode=true is the default, with Japanese (platex), the option
// leads to errors (even if the input encoding is UTF-8).)
if (!runparams.isFullUnicode() && !runparams.use_japanese)
opt += "unicode=true,";
That is: LyX outputs unicode itself in some cases, so setting
unicode=false could lead to errors. Still, it might be worth a document
preference on this.
Riki
An alternative might be to set the "Additional Options" via the package
options rather than hypersetup.
Daniel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 3/19/20 3:01 AM, Daniel wrote:
> On 2020-03-18 14:59, Steve Hnizdur wrote:
>> Hi
>>
>> When "Use Hyperref Support" is checked in PDF properties Lyx
>> automatically inserts
>>
>> \usepackage[unicode=true,
>> bookmarks=false,
>> breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
>> {hyperref}
>>
>> in the preamble. Any ideas where all these options come from? are
>> they hard coded?
>>
>> Setting "unicode=false" in additional options doesn't seem to
>> override the "unicode=true". So if unicode=true is causing a problem
>> (in particular trying to redefine \C or \G) then this all has to
>> added manually.
>>
>> MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
>>
>
> Hi
>
> Yes, these options come from settings in the Hyperref dialog.
>
> "bookmarks=..." = "Generate bookmars (toc)"
> "breaklinks=..." = "Break links over lines"
> "pdfborder=..." = "No frames around links"
> "colorlinks=..." = "Color links"
> "backref=..." = "Backreferences"
>
> However, there seems to be no option for the "unicode=..." which seems
> like an oversight. And the biggest problem is that according to the
> manual:
>
> Note however that some options (for example unicode) can only be used
> as packge options,and not in \hypersetup as the option settings are
> processed as the package is read. (p. 6)
>
> So, unicode=false has no effect as an additional option.
>
> My guess is that this is a bug in LyX but others might know better.
Well, the code is:
// Since LyX uses unicode, also set the PDF strings to unicode strings
// with the hyperref option "unicode". (With Xe/LuaTeX and pTeX,
// unicode=true is the default, with Japanese (platex), the option
// leads to errors (even if the input encoding is UTF-8).)
if (!runparams.isFullUnicode() && !runparams.use_japanese)
opt += "unicode=true,";
That is: LyX outputs unicode itself in some cases, so setting
unicode=false could lead to errors. Still, it might be worth a document
preference on this.
Riki
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Hyperref support
On 2020-03-18 14:59, Steve Hnizdur wrote:
Hi
When "Use Hyperref Support" is checked in PDF properties Lyx
automatically inserts
\usepackage[unicode=true,
bookmarks=false,
breaklinks=false,pdfborder={0 0 1},backref=section,colorlinks=false]
{hyperref}
in the preamble. Any ideas where all these options come from? are they
hard coded?
Setting "unicode=false" in additional options doesn't seem to override
the "unicode=true". So if unicode=true is causing a problem (in
particular trying to redefine \C or \G) then this all has to added
manually.
MWE attached. Using Lyx 2.3.4.2 on Ubuntu 18.04
Hi
Yes, these options come from settings in the Hyperref dialog.
"bookmarks=..." = "Generate bookmars (toc)"
"breaklinks=..." = "Break links over lines"
"pdfborder=..." = "No frames around links"
"colorlinks=..." = "Color links"
"backref=..." = "Backreferences"
However, there seems to be no option for the "unicode=..." which seems
like an oversight. And the biggest problem is that according to the manual:
Note however that some options (for example unicode) can only be used as
packge options,and not in \hypersetup as the option settings are
processed as the package is read. (p. 6)
So, unicode=false has no effect as an additional option.
My guess is that this is a bug in LyX but others might know better.
Daniel
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
