Re: Font (detection) problems (want to use a Garamond font)

[Christian Obst]

Thanks, I just created the links, that solves it for me! I'll dive
into the font management some other time, but this is all very
helpful!

On Sat, May 6, 2023 at 3:31 AM Dr Eberhard Lisse  wrote:
>
> I am wondering if texhash looks for fonts and if so if it configured to
> see the path. Something for the experts...
>
> I would NOT copy but only symlink so that an update (in /opt) will
> automatically pull through.  Otherwise you have to remember to repeat
> the copy.
>
> el
>
> On 2023-05-06 00:29 , Christian Obst wrote:
> > I'll try that, thank you!  I already copied the one font, I'll try the
> > linking option later.
> >
> > Eckhard Höffner  schrieb am Fr., 5. Mai 2023, 
> > 16:57:
> >
> > There are several options.  An easy way could be links from the
> > opentype and ttf dirs under your tex-tree to
> > /usr/local/share/fonts or to $HOME/.local/share/fonts/
> >
> > I don't know your current situation, but it may be something like:
> >
> > mkdir $HOME/.local/share/fonts/texfonts
> >
> > cd $HOME/.local/share/fonts/texfonts
> >
> > ln -s /opt/texlive/texmf-dist/fonts/opentype ./
> >
> > ln -s /opt/texlive/texmf-dist/fonts/ttf ./
> >
> > I hope, this works.
> [...]
>
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Font (detection) problems (want to use a Garamond font)

[Christian Obst]

I'll try that, thank you! I already copied the one font, I'll try the
linking option later.

Eckhard Höffner  schrieb am Fr., 5. Mai 2023,
16:57:

> There are several options. An easy way could be links from the opentype
> and ttf dirs under your tex-tree to /usr/local/share/fonts or to
> $HOME/.local/share/fonts/
>
> I don't know your current situation, but it may be something like:
>
> mkdir $HOME/.local/share/fonts/texfonts
>
> cd $HOME/.local/share/fonts/texfonts
>
> ln -s /opt/texlive/texmf-dist/fonts/opentype ./
>
> ln -s /opt/texlive/texmf-dist/fonts/ttf ./
>
> I hope, this works.
>
>
> I don't know the reason, why pdflatex does not find the fonts, because
> latex has its own "database" for files. Maybe some font files are
> missing or you need to run mktexlsr (as root).
>
>
>
>
> Am 05.05.23 um 20:24 schrieb Christian Obst:
> > (Should I reply to both the list and the sender, or just the list?)
> Sorry, my mistake ...
> >
> > That's interesting! Libreoffice or fc-list doesn't see it, either! Why
> > does the TexLive installer install to /opt if that's not normal?
> >
> > I can also see that in /etc/fonts/conf.d/, there are many config files
> > (including urw-*) which link to /usr/share/fontconfig/conf.avail/, but
> > none for garamond. How come other fonts installed by tlmgr are
> > visible, but not all? Even of they are installed in /opt? Should I
> > reinstall TexLive to another location? What's the default location?
> >
> >
> >
> > On Fri, May 5, 2023 at 1:40 PM Eckhard Höffner
> >  wrote:
> >> Maybe it's because they are in /opt. I don't assume I'm right, but if
> you look a /etc/fonts/fonts.conf (or a subdirectory), /opt is not a usual
> fontpath.
> >>
> >> fc-list | grep garamond
> >>
> >> is another method.
> >>
> >> Are other programs showing the fonts (e. g. libreoffice).
> >>
> >> You can also copy the fonts you want (otf // ttf) to
> HOME/.local/share/fonts/ (or /usr/local/share/fonts); both should be in the
> font path of al programs.  My LyX and fontspec (debian) have no problems
> using the HOME-directory.
> >>
> >>
> >>
> >>
> >>
> >> Am 05.05.23 um 17:22 schrieb Christian Obst:
> >>
> >> Hi all,
> >>
> >> I'm using LyX 2.3.7, and TexLive 2023 (via tlmgr, not distro) on Void
> >> Linux. My problem is that I can't use any of the Garamond fonts
> >> installed (URW, EB). LyX has been configured via Tools -> Reconfigure,
> >> and the PATH (to /opt/texlive/2023/bin/x86_64-linux) is set. LyX finds
> >> all installed packages etc.
> >>
> >> If I try to use "URW Garamond (Mathdesign)", I get an error when
> compiling:
> >>
> >> !pdfTeX error: pdflatex (file ugmm8a.pfb): cannot open Type 1 font
> >> file for reading.
> >>
> >> "URW Garamond" (no Mathdesign) is listed as "not installed", even
> >> though it is according to tlmgr.
> >>
> >> If I switch to "Don't use TeX-Fonts" in the font dialog, EB Garamond
> >> is not listed at all, but it is installed. Weirdly, old LyX documents
> >> that use that font still compile fine and display it in the output. I
> >> also used to be able (until a week ago) to manually set the main font
> >> to "EB Garamond" using
> >>
> >> \usepackage{fontspec}
> >> \setmainfont{EB Garamond}
> >>
> >> but that no longer works (gives me an error about not finding that
> >> font). luaotfload-tool --find "EBGaramond" confirms that it is
> >> installed in
> "/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/EBGaramond-Regular.otf"
> >>
> >> I am thoroughly confused, and don't even know where to begin checking.
> >> Any help is appreciated!
> >>
> >> Best regards,
> >> Christian
> >>
>
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Font (detection) problems (want to use a Garamond font)

[Christian Obst]

(Should I reply to both the list and the sender, or just the list?)

That's interesting! Libreoffice or fc-list doesn't see it, either! Why
does the TexLive installer install to /opt if that's not normal?

I can also see that in /etc/fonts/conf.d/, there are many config files
(including urw-*) which link to /usr/share/fontconfig/conf.avail/, but
none for garamond. How come other fonts installed by tlmgr are
visible, but not all? Even of they are installed in /opt? Should I
reinstall TexLive to another location? What's the default location?



On Fri, May 5, 2023 at 1:40 PM Eckhard Höffner
 wrote:
>
> Maybe it's because they are in /opt. I don't assume I'm right, but if you 
> look a /etc/fonts/fonts.conf (or a subdirectory), /opt is not a usual 
> fontpath.
>
> fc-list | grep garamond
>
> is another method.
>
> Are other programs showing the fonts (e. g. libreoffice).
>
> You can also copy the fonts you want (otf // ttf) to HOME/.local/share/fonts/ 
> (or /usr/local/share/fonts); both should be in the font path of al programs.  
> My LyX and fontspec (debian) have no problems using the HOME-directory.
>
>
>
>
>
> Am 05.05.23 um 17:22 schrieb Christian Obst:
>
> Hi all,
>
> I'm using LyX 2.3.7, and TexLive 2023 (via tlmgr, not distro) on Void
> Linux. My problem is that I can't use any of the Garamond fonts
> installed (URW, EB). LyX has been configured via Tools -> Reconfigure,
> and the PATH (to /opt/texlive/2023/bin/x86_64-linux) is set. LyX finds
> all installed packages etc.
>
> If I try to use "URW Garamond (Mathdesign)", I get an error when compiling:
>
> !pdfTeX error: pdflatex (file ugmm8a.pfb): cannot open Type 1 font
> file for reading.
>
> "URW Garamond" (no Mathdesign) is listed as "not installed", even
> though it is according to tlmgr.
>
> If I switch to "Don't use TeX-Fonts" in the font dialog, EB Garamond
> is not listed at all, but it is installed. Weirdly, old LyX documents
> that use that font still compile fine and display it in the output. I
> also used to be able (until a week ago) to manually set the main font
> to "EB Garamond" using
>
> \usepackage{fontspec}
> \setmainfont{EB Garamond}
>
> but that no longer works (gives me an error about not finding that
> font). luaotfload-tool --find "EBGaramond" confirms that it is
> installed in 
> "/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/EBGaramond-Regular.otf"
>
> I am thoroughly confused, and don't even know where to begin checking.
> Any help is appreciated!
>
> Best regards,
> Christian
>
> --
> Eckhard Höffner
> Volkarstr. 64
> D-80636 München
> Tel.: 089 210 31 888
>
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Font (detection) problems (want to use a Garamond font)

[Christian Obst]

Here it is:

No. Filename
   Path
  1.   CormorantGaramond-Bold.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  2. CormorantGaramond-BoldItalic.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  3. CormorantGaramond-Italic.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  4.  CormorantGaramond-Light.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  5.CormorantGaramond-LightItalic.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  6. CormorantGaramond-Medium.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  7.   CormorantGaramond-MediumItalic.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  8.CormorantGaramond-Regular.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
  9.   CormorantGaramond-SemiBold.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
 10. CormorantGaramond-SemiBoldItalic.ttf
/opt/texlive/2023/texmf-dist/fonts/truetype/catharsis/cormorantgaramond/
 11.  EBGaramond-Bold.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 12.EBGaramond-BoldItalic.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 13. EBGaramond-ExtraBold.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 14.   EBGaramond-ExtraBoldItalic.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 15.  EBGaramond-Initials.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 16.EBGaramond-Italic.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 17.EBGaramond-Medium.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 18.  EBGaramond-MediumItalic.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 19.   EBGaramond-Regular.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 20.  EBGaramond-SemiBold.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 21.EBGaramond-SemiBoldItalic.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/
 22.Garamond-Math.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/garamond-math/
 23.   GaramondLibre-Bold.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/garamond-libre/
 24. GaramondLibre-BoldItalic.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/garamond-libre/
 25. GaramondLibre-Italic.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/garamond-libre/
 26.GaramondLibre-Regular.otf
/opt/texlive/2023/texmf-dist/fonts/opentype/public/garamond-libre/

On Fri, May 5, 2023 at 11:29 AM Herbert Voss  wrote:
>
> Am 05.05.23 um 17:22 schrieb Christian Obst:
> > \usepackage{fontspec}
> > \setmainfont{EB Garamond}
> >
> > but that no longer works (gives me an error about not finding that
> > font). luaotfload-tool --find "EBGaramond" confirms that it is
> > installed in 
> > "/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/EBGaramond-Regular.otf"
>
> What is the output of
>
> luafindfont -n garamond
>
> ??
>
> Herbert
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Font (detection) problems (want to use a Garamond font)

[Christian Obst]

Hi all,

I'm using LyX 2.3.7, and TexLive 2023 (via tlmgr, not distro) on Void
Linux. My problem is that I can't use any of the Garamond fonts
installed (URW, EB). LyX has been configured via Tools -> Reconfigure,
and the PATH (to /opt/texlive/2023/bin/x86_64-linux) is set. LyX finds
all installed packages etc.

If I try to use "URW Garamond (Mathdesign)", I get an error when compiling:

!pdfTeX error: pdflatex (file ugmm8a.pfb): cannot open Type 1 font
file for reading.

"URW Garamond" (no Mathdesign) is listed as "not installed", even
though it is according to tlmgr.

If I switch to "Don't use TeX-Fonts" in the font dialog, EB Garamond
is not listed at all, but it is installed. Weirdly, old LyX documents
that use that font still compile fine and display it in the output. I
also used to be able (until a week ago) to manually set the main font
to "EB Garamond" using

\usepackage{fontspec}
\setmainfont{EB Garamond}

but that no longer works (gives me an error about not finding that
font). luaotfload-tool --find "EBGaramond" confirms that it is
installed in 
"/opt/texlive/2023/texmf-dist/fonts/opentype/public/ebgaramond/EBGaramond-Regular.otf"

I am thoroughly confused, and don't even know where to begin checking.
Any help is appreciated!

Best regards,
Christian
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: EBGaramond listed as "Not installed" ("Don't use TeX fonts" is checked)

[Christian Obst]

Yes, I did!

Am 14. März 2023 11:38:31 GMT-04:00 schrieb Richard Kimberly Heck 
:
>On 3/13/23 22:58, Christian Obst wrote:
>> Hello fellow LyX users,
>> 
>> I installed EBGaramond via TexLive's tlmgr. I also have old documents
>> (previous installs), which use that font, and they compile fine
>> (correct font, looks great).
>> 
>> However, in the Document settings, EBGaramond is shown as "Not
>> installed."
>
>Did you Tools > Reconfigure after installing the new font?
>
>Riki
>
>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

EBGaramond listed as "Not installed" ("Don't use TeX fonts" is checked)

[Christian Obst]

Hello fellow LyX users,

I installed EBGaramond via TexLive's tlmgr. I also have old documents
(previous installs), which use that font, and they compile fine
(correct font, looks great).

However, in the Document settings, EBGaramond is shown as "Not
installed." In new docs, I can't select it. luaotfload-tool confirms
EBGaramond is indeed installed. Lyx does show me tons of other Opentype
fonts, but not EBGaramond. Of course, I reconfigured Lyx and restarted
after installing the font.

If I uncheck "Don't use TeX fonts," it lists "URW Garamond," but also
as "Not installed."

Latex/LuaTex apparently is not the issue, as the document preamble
(generated by Lyx) contains "\setmainfont[Ligatures=TeX]{EB Garamond},"
and it compiles fine.

I used to be able previously to select EBGaramond, but that was a
different Linux distro, and I installed that font from the distro's
repos. Now, I installed it from CTAN servers, as my current distro does
not have it.

I'm using TexLive 2022. Admittedly, I'm clueless about the world of
fonts, and I may be confused by something.

How can I fix Lyx so it lets me select my preferred font?

(I'm also not a subscriber to lyx-users currently, if that information
is necessary.)

Best regards to all,
Christian
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Tue, 18 Sep 2012 21:16:44 -0500
schrieb stefano franchi stefano.fran...@gmail.com:

 Actually, I had missed your example.zip file, sorry. I imported the
 tex file into Lyx, and it compiles with no issues. I am attaching the
 pdf page. Is that the output  you wanted?

That you can compile it makes me think there is something somewhere in
my configs that messes things up. Maybe I should test with a fresh lyx
config.

I installed 2011 in my home dir, this works without problems. So at
least it's not so urgent anymore.

Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Tue, 18 Sep 2012 21:16:44 -0500
schrieb stefano franchi stefano.fran...@gmail.com:

 Actually, I had missed your example.zip file, sorry. I imported the
 tex file into Lyx, and it compiles with no issues. I am attaching the
 pdf page. Is that the output  you wanted?

That you can compile it makes me think there is something somewhere in
my configs that messes things up. Maybe I should test with a fresh lyx
config.

I installed 2011 in my home dir, this works without problems. So at
least it's not so urgent anymore.

Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Tue, 18 Sep 2012 21:16:44 -0500
schrieb stefano franchi :

> Actually, I had missed your example.zip file, sorry. I imported the
> tex file into Lyx, and it compiles with no issues. I am attaching the
> pdf page. Is that the output  you wanted?

That you can compile it makes me think there is something somewhere in
my configs that messes things up. Maybe I should test with a fresh lyx
config.

I installed 2011 in my home dir, this works without problems. So at
least it's not so urgent anymore.

Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Wed, 12 Sep 2012 17:57:34 -0400
schrieb Richard Heck rgh...@lyx.org:

 On 09/12/2012 01:48 PM, Christian Obst wrote:
  Hi,
 
  I have this strange problem. A document which was previously working
  cannot be compiled anymore because latex complains about unbalanced
  brackets or parentheses in a foot- or endnote. If I manually
  convert to .tex and look at the resulting file, I find passages
  like this:
 
  texttexttext.%
  \footnote{Texinfootnote.%
  }
 
  First, I dont understand why lyx is putting the percentage signs
  there, they are regular footnotes, not comments. Also, I thought
  they are supposed to xcomment out the rest of the line, not what is
  enclosed between two of them. However, they leave one bracket out,
  so I think this is what produces my error.
 That is perfectly OK code. The %s do exactly what you say, so there's 
 nothing unbalanced there (and nothing in that part of the LyX code
 has changed recently). The problem is surely elsewhere. I'd suggest
 you try bisecting: removing chunks until you get something that
 works, then adding stuff back, etc.

Ok, I now tried something else, which gives me weird results. I
exported the document to Latex (normal), and ran latex on that file. It
gave me the same biblatex error (unbalanced brackets or parantheses). I
quit, ran bibtex on the document anyway, which finished with many errors
about whitespaces in the aux. Now the weird part: I ran latex again,
it gave me no error and produced a dvi. Now, I reran bibtext, as well,
which finished without errors, as well, and so did any subsequent latex
runs. I did not edit the tex file or anything.

So basically, the document seems to be fine (no more unbalanced
brackets after latex/bibtex runs), but somehow it isn't so in the
beginning.

How can that be?

Many thanks,
Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Fri, 14 Sep 2012 11:53:52 -0500
schrieb stefano franchi stefano.fran...@gmail.com:


 Now, for your problem, here is a stab:  If I understand you correctly,
 biblatex gave you problems, whereas bibtex (after a few runs) gave you
 correct output. You may want to check that your biblatex version and
 your biblatex style are in sync. The errors you are reporting are
 rather typical of a mismatch of this kind. You may have older versions
 of the standard biblatex styles on your system picked up by mistake,
 or you may be using custom biblatex styles (which usually lag behind
 biblatex rather frantic development pace).

Ok, thanks. I use indeed a custom biblatex style: biblatex-dw. On my
system (Sabayon Linux, based on Gentoo testing), biblatex-dw is in the
package bibtexextra, which is from the 2012 texlive distro. Biblatex
itself is its own package, and installed version is 2.1-r1. 2.1 seems
to be from 2012 as well, but there is biblatex 2.2, too (not yet in my
distros repos).

Could those two version be incompatible? They seem recent to me.

Is it possible to install my own version (i.e. 2.2) of biblatex in my
home dir? How would I point Lyx to use it?

Many thanks again,
Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Wed, 12 Sep 2012 17:57:34 -0400
schrieb Richard Heck rgh...@lyx.org:

 On 09/12/2012 01:48 PM, Christian Obst wrote:
  Hi,
 
  I have this strange problem. A document which was previously working
  cannot be compiled anymore because latex complains about unbalanced
  brackets or parentheses in a foot- or endnote. If I manually
  convert to .tex and look at the resulting file, I find passages
  like this:
 
  texttexttext.%
  \footnote{Texinfootnote.%
  }
 
  First, I dont understand why lyx is putting the percentage signs
  there, they are regular footnotes, not comments. Also, I thought
  they are supposed to xcomment out the rest of the line, not what is
  enclosed between two of them. However, they leave one bracket out,
  so I think this is what produces my error.
 That is perfectly OK code. The %s do exactly what you say, so there's 
 nothing unbalanced there (and nothing in that part of the LyX code
 has changed recently). The problem is surely elsewhere. I'd suggest
 you try bisecting: removing chunks until you get something that
 works, then adding stuff back, etc.

Ok, I now tried something else, which gives me weird results. I
exported the document to Latex (normal), and ran latex on that file. It
gave me the same biblatex error (unbalanced brackets or parantheses). I
quit, ran bibtex on the document anyway, which finished with many errors
about whitespaces in the aux. Now the weird part: I ran latex again,
it gave me no error and produced a dvi. Now, I reran bibtext, as well,
which finished without errors, as well, and so did any subsequent latex
runs. I did not edit the tex file or anything.

So basically, the document seems to be fine (no more unbalanced
brackets after latex/bibtex runs), but somehow it isn't so in the
beginning.

How can that be?

Many thanks,
Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Fri, 14 Sep 2012 11:53:52 -0500
schrieb stefano franchi stefano.fran...@gmail.com:


 Now, for your problem, here is a stab:  If I understand you correctly,
 biblatex gave you problems, whereas bibtex (after a few runs) gave you
 correct output. You may want to check that your biblatex version and
 your biblatex style are in sync. The errors you are reporting are
 rather typical of a mismatch of this kind. You may have older versions
 of the standard biblatex styles on your system picked up by mistake,
 or you may be using custom biblatex styles (which usually lag behind
 biblatex rather frantic development pace).

Ok, thanks. I use indeed a custom biblatex style: biblatex-dw. On my
system (Sabayon Linux, based on Gentoo testing), biblatex-dw is in the
package bibtexextra, which is from the 2012 texlive distro. Biblatex
itself is its own package, and installed version is 2.1-r1. 2.1 seems
to be from 2012 as well, but there is biblatex 2.2, too (not yet in my
distros repos).

Could those two version be incompatible? They seem recent to me.

Is it possible to install my own version (i.e. 2.2) of biblatex in my
home dir? How would I point Lyx to use it?

Many thanks again,
Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Wed, 12 Sep 2012 17:57:34 -0400
schrieb Richard Heck <rgh...@lyx.org>:

> On 09/12/2012 01:48 PM, Christian Obst wrote:
> > Hi,
> >
> > I have this strange problem. A document which was previously working
> > cannot be compiled anymore because latex complains about "unbalanced
> > brackets or parentheses in a foot- or endnote". If I manually
> > convert to .tex and look at the resulting file, I find passages
> > like this:
> >
> > texttexttext.%
> > \footnote{Texinfootnote.%
> > }
> >
> > First, I dont understand why lyx is putting the percentage signs
> > there, they are regular footnotes, not comments. Also, I thought
> > they are supposed to xcomment out the rest of the line, not what is
> > enclosed between two of them. However, they leave one bracket out,
> > so I think this is what produces my error.
> That is perfectly OK code. The %s do exactly what you say, so there's 
> nothing unbalanced there (and nothing in that part of the LyX code
> has changed recently). The problem is surely elsewhere. I'd suggest
> you try bisecting: removing chunks until you get something that
> works, then adding stuff back, etc.

Ok, I now tried something else, which gives me weird results. I
exported the document to Latex (normal), and ran latex on that file. It
gave me the same biblatex error (unbalanced brackets or parantheses). I
quit, ran bibtex on the document anyway, which finished with many errors
about "whitespaces" in the aux. Now the weird part: I ran latex again,
it gave me no error and produced a dvi. Now, I reran bibtext, as well,
which finished without errors, as well, and so did any subsequent latex
runs. I did not edit the tex file or anything.

So basically, the document seems to be fine (no more unbalanced
brackets after latex/bibtex runs), but somehow it isn't so in the
beginning.

How can that be?

Many thanks,
Christian

Re: Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Am Fri, 14 Sep 2012 11:53:52 -0500
schrieb stefano franchi :


> Now, for your problem, here is a stab:  If I understand you correctly,
> biblatex gave you problems, whereas bibtex (after a few runs) gave you
> correct output. You may want to check that your biblatex version and
> your biblatex style are in sync. The errors you are reporting are
> rather typical of a mismatch of this kind. You may have older versions
> of the standard biblatex styles on your system picked up by mistake,
> or you may be using custom biblatex styles (which usually lag behind
> biblatex rather frantic development pace).

Ok, thanks. I use indeed a custom biblatex style: biblatex-dw. On my
system (Sabayon Linux, based on Gentoo testing), biblatex-dw is in the
package bibtexextra, which is from the 2012 texlive distro. Biblatex
itself is its own package, and installed version is 2.1-r1. 2.1 seems
to be from 2012 as well, but there is biblatex 2.2, too (not yet in my
distros repos).

Could those two version be incompatible? They seem recent to me.

Is it possible to install my own version (i.e. 2.2) of biblatex in my
home dir? How would I point Lyx to use it?

Many thanks again,
Christian

Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Hi,

I have this strange problem. A document which was previously working
cannot be compiled anymore because latex complains about unbalanced
brackets or parentheses in a foot- or endnote. If I manually convert
to .tex and look at the resulting file, I find passages like this:

texttexttext.%
\footnote{Texinfootnote.%
}

First, I dont understand why lyx is putting the percentage signs there,
they are regular footnotes, not comments. Also, I thought they
are supposed to xcomment out the rest of the line, not what is enclosed
between two of them. However, they leave one bracket out, so I think
this is what produces my error.

My texlive packages are all uptodate (however recently updated), and I
also ran Tools-Reconfigure.

This problem exists for me in the stable version and the one from git.

Any help?

Best regards,
Christian

Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Hi,

I have this strange problem. A document which was previously working
cannot be compiled anymore because latex complains about unbalanced
brackets or parentheses in a foot- or endnote. If I manually convert
to .tex and look at the resulting file, I find passages like this:

texttexttext.%
\footnote{Texinfootnote.%
}

First, I dont understand why lyx is putting the percentage signs there,
they are regular footnotes, not comments. Also, I thought they
are supposed to xcomment out the rest of the line, not what is enclosed
between two of them. However, they leave one bracket out, so I think
this is what produces my error.

My texlive packages are all uptodate (however recently updated), and I
also ran Tools-Reconfigure.

This problem exists for me in the stable version and the one from git.

Any help?

Best regards,
Christian

Lyx misplacing brackets when converting to latex, cannot produce pdf

[Christian Obst]

Hi,

I have this strange problem. A document which was previously working
cannot be compiled anymore because latex complains about "unbalanced
brackets or parentheses in a foot- or endnote". If I manually convert
to .tex and look at the resulting file, I find passages like this:

texttexttext.%
\footnote{Texinfootnote.%
}

First, I dont understand why lyx is putting the percentage signs there,
they are regular footnotes, not comments. Also, I thought they
are supposed to xcomment out the rest of the line, not what is enclosed
between two of them. However, they leave one bracket out, so I think
this is what produces my error.

My texlive packages are all uptodate (however recently updated), and I
also ran Tools->Reconfigure.

This problem exists for me in the stable version and the one from git.

Any help?

Best regards,
Christian

Trouble after upgrading to TexLive 2012

[Christian Obst]

Hi,

I think when my distro (Sabayon, Gentoo-based) upgraded to TL 2012,
some things broke. I have a document (scrartcl), in which I use
biblatex(-dw) for my bibliography and citations. Some time around when
the updates came, Lyx (2.0.4) stopped being able to produce pdf. Instead
I get tons of Undefined control sequence errors. According to the full
latex output, it seems to be a problem with bibtex or biblatex, but I
cannot figure it out. Somewhere in the log (attached) it says:

Package biblatex Warning: File 'LeTresHaut.bbl' is wrong format version
- expec ted 2.1.

But my biblatex package was upgraded along with TexLive, and bibtex -v
gives me BibTeX 0.99d (TeX Live 2012).

Is this maybe a known problem when migrating from 2011 to 2012?

I will have to turn that paper in, eventually, so I need it working
again. Please help me!

Many thanks in advance,
ChristianThis is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012) (format=pdflatex 
2012.8.16)  18 AUG 2012 21:28
entering extended mode
 restricted \write18 enabled.
 %-line parsing enabled.
**LeTresHaut.tex
(./LeTresHaut.tex
LaTeX2e 2011/06/27
Babel v3.8m and hyphenation patterns for english, dumylang, nohyphenation, ge
rman-x-2012-05-30, ngerman-x-2012-05-30, german, ngerman, swissgerman, loaded.

(/usr/share/texmf-dist/tex/latex/koma-script/scrartcl.cls
Document Class: scrartcl 2012/05/15 v3.11 KOMA-Script document class (article)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2012/05/15 v3.11 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2012/05/15 v3.11 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
\KV@toks@=\toks14
) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2011/03/09 v3.09 KOMA-Script package (loading files)
Package scrlfile, 2011/03/09 v3.09 KOMA-Script package (loading files)
  Copyright (C) Markus Kohm

))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2012/04/04 v3.10b KOMA-Script package (handling toc-files)
)
Package tocbasic Info: omitting babel extension for `toc'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `toc' on input line 115.
Package tocbasic Info: omitting babel extension for `lof'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lof' on input line 116.
Package tocbasic Info: omitting babel extension for `lot'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lot' on input line 117.
Package scrartcl Info: You've used obsolete option `12pt'.
(scrartcl) \KOMAExecuteOptions{fontsize=12pt} will be
(scrartcl) used instead.
(scrartcl) You may simply replace `12pt'
(scrartcl) by `fontsize=12pt'.
Class scrartcl Info: File `scrsize12pt.clo' used to setup font sizes on input l
ine 1265.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize12pt.clo
File: scrsize12pt.clo 2012/05/15 v3.11 KOMA-Script font size class option (12pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2012/05/15 v3.11 KOMA-Script package (type area)
Package typearea, 2012/05/15 v3.11 KOMA-Script package (type area)
  Copyright (C) Frank Neukam, 1992-1994
  Copyright (C) Markus Kohm, 1994-

\ta@bcor=\skip41
\ta@div=\count79
Package typearea Info: You've used standard option `a4paper'.
(typearea) This is correct!
(typearea) Internally I'm using `paper=a4'.
(typearea) If you'd like to set the option with \KOMAoptions,
(typearea) you'd have to use `paper=a4' there
(typearea) instead of `a4paper', too.
\ta@hblk=\skip42
\ta@vblk=\skip43
\ta@temp=\skip44
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 12
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 448.13095pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 2.4185pt
(typearea)  \oddsidemargin  = 2.4185pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 635.5pt
(typearea)  \topmargin  = -41.72441pt
(typearea)  \headheight = 18.125pt
(typearea)  \headsep= 21.75pt
(typearea)  \topskip= 12.0pt
(typearea)  \footskip   = 50.75pt
(typearea)  \baselineskip   = 14.5pt
(typearea)  on input line 1211.
)
\c@part=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\abovecaptionskip=\skip45

Trouble after upgrading to TexLive 2012

[Christian Obst]

Hi,

I think when my distro (Sabayon, Gentoo-based) upgraded to TL 2012,
some things broke. I have a document (scrartcl), in which I use
biblatex(-dw) for my bibliography and citations. Some time around when
the updates came, Lyx (2.0.4) stopped being able to produce pdf. Instead
I get tons of Undefined control sequence errors. According to the full
latex output, it seems to be a problem with bibtex or biblatex, but I
cannot figure it out. Somewhere in the log (attached) it says:

Package biblatex Warning: File 'LeTresHaut.bbl' is wrong format version
- expec ted 2.1.

But my biblatex package was upgraded along with TexLive, and bibtex -v
gives me BibTeX 0.99d (TeX Live 2012).

Is this maybe a known problem when migrating from 2011 to 2012?

I will have to turn that paper in, eventually, so I need it working
again. Please help me!

Many thanks in advance,
ChristianThis is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012) (format=pdflatex 
2012.8.16)  18 AUG 2012 21:28
entering extended mode
 restricted \write18 enabled.
 %-line parsing enabled.
**LeTresHaut.tex
(./LeTresHaut.tex
LaTeX2e 2011/06/27
Babel v3.8m and hyphenation patterns for english, dumylang, nohyphenation, ge
rman-x-2012-05-30, ngerman-x-2012-05-30, german, ngerman, swissgerman, loaded.

(/usr/share/texmf-dist/tex/latex/koma-script/scrartcl.cls
Document Class: scrartcl 2012/05/15 v3.11 KOMA-Script document class (article)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2012/05/15 v3.11 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2012/05/15 v3.11 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
\KV@toks@=\toks14
) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2011/03/09 v3.09 KOMA-Script package (loading files)
Package scrlfile, 2011/03/09 v3.09 KOMA-Script package (loading files)
  Copyright (C) Markus Kohm

))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2012/04/04 v3.10b KOMA-Script package (handling toc-files)
)
Package tocbasic Info: omitting babel extension for `toc'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `toc' on input line 115.
Package tocbasic Info: omitting babel extension for `lof'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lof' on input line 116.
Package tocbasic Info: omitting babel extension for `lot'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lot' on input line 117.
Package scrartcl Info: You've used obsolete option `12pt'.
(scrartcl) \KOMAExecuteOptions{fontsize=12pt} will be
(scrartcl) used instead.
(scrartcl) You may simply replace `12pt'
(scrartcl) by `fontsize=12pt'.
Class scrartcl Info: File `scrsize12pt.clo' used to setup font sizes on input l
ine 1265.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize12pt.clo
File: scrsize12pt.clo 2012/05/15 v3.11 KOMA-Script font size class option (12pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2012/05/15 v3.11 KOMA-Script package (type area)
Package typearea, 2012/05/15 v3.11 KOMA-Script package (type area)
  Copyright (C) Frank Neukam, 1992-1994
  Copyright (C) Markus Kohm, 1994-

\ta@bcor=\skip41
\ta@div=\count79
Package typearea Info: You've used standard option `a4paper'.
(typearea) This is correct!
(typearea) Internally I'm using `paper=a4'.
(typearea) If you'd like to set the option with \KOMAoptions,
(typearea) you'd have to use `paper=a4' there
(typearea) instead of `a4paper', too.
\ta@hblk=\skip42
\ta@vblk=\skip43
\ta@temp=\skip44
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 12
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 448.13095pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 2.4185pt
(typearea)  \oddsidemargin  = 2.4185pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 635.5pt
(typearea)  \topmargin  = -41.72441pt
(typearea)  \headheight = 18.125pt
(typearea)  \headsep= 21.75pt
(typearea)  \topskip= 12.0pt
(typearea)  \footskip   = 50.75pt
(typearea)  \baselineskip   = 14.5pt
(typearea)  on input line 1211.
)
\c@part=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\abovecaptionskip=\skip45

Trouble after upgrading to TexLive 2012

[Christian Obst]

Hi,

I think when my distro (Sabayon, Gentoo-based) upgraded to TL 2012,
some things broke. I have a document (scrartcl), in which I use
biblatex(-dw) for my bibliography and citations. Some time around when
the updates came, Lyx (2.0.4) stopped being able to produce pdf. Instead
I get tons of "Undefined control sequence" errors. According to the full
latex output, it seems to be a problem with bibtex or biblatex, but I
cannot figure it out. Somewhere in the log (attached) it says:

Package biblatex Warning: File 'LeTresHaut.bbl' is wrong format version
- expec ted 2.1.

But my biblatex package was upgraded along with TexLive, and bibtex -v
gives me BibTeX 0.99d (TeX Live 2012).

Is this maybe a known problem when migrating from 2011 to 2012?

I will have to turn that paper in, eventually, so I need it working
again. Please help me!

Many thanks in advance,
ChristianThis is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012) (format=pdflatex 
2012.8.16)  18 AUG 2012 21:28
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**LeTresHaut.tex
(./LeTresHaut.tex
LaTeX2e <2011/06/27>
Babel  and hyphenation patterns for english, dumylang, nohyphenation, ge
rman-x-2012-05-30, ngerman-x-2012-05-30, german, ngerman, swissgerman, loaded.

(/usr/share/texmf-dist/tex/latex/koma-script/scrartcl.cls
Document Class: scrartcl 2012/05/15 v3.11 KOMA-Script document class (article)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2012/05/15 v3.11 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2012/05/15 v3.11 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
\KV@toks@=\toks14
) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2011/03/09 v3.09 KOMA-Script package (loading files)
Package scrlfile, 2011/03/09 v3.09 KOMA-Script package (loading files)
  Copyright (C) Markus Kohm

))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2012/04/04 v3.10b KOMA-Script package (handling toc-files)
)
Package tocbasic Info: omitting babel extension for `toc'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `toc' on input line 115.
Package tocbasic Info: omitting babel extension for `lof'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lof' on input line 116.
Package tocbasic Info: omitting babel extension for `lot'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lot' on input line 117.
Package scrartcl Info: You've used obsolete option `12pt'.
(scrartcl) \KOMAExecuteOptions{fontsize=12pt} will be
(scrartcl) used instead.
(scrartcl) You may simply replace `12pt'
(scrartcl) by `fontsize=12pt'.
Class scrartcl Info: File `scrsize12pt.clo' used to setup font sizes on input l
ine 1265.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize12pt.clo
File: scrsize12pt.clo 2012/05/15 v3.11 KOMA-Script font size class option (12pt
)
) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2012/05/15 v3.11 KOMA-Script package (type area)
Package typearea, 2012/05/15 v3.11 KOMA-Script package (type area)
  Copyright (C) Frank Neukam, 1992-1994
  Copyright (C) Markus Kohm, 1994-

\ta@bcor=\skip41
\ta@div=\count79
Package typearea Info: You've used standard option `a4paper'.
(typearea) This is correct!
(typearea) Internally I'm using `paper=a4'.
(typearea) If you'd like to set the option with \KOMAoptions,
(typearea) you'd have to use `paper=a4' there
(typearea) instead of `a4paper', too.
\ta@hblk=\skip42
\ta@vblk=\skip43
\ta@temp=\skip44
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 12
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 448.13095pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 2.4185pt
(typearea)  \oddsidemargin  = 2.4185pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 635.5pt
(typearea)  \topmargin  = -41.72441pt
(typearea)  \headheight = 18.125pt
(typearea)  \headsep= 21.75pt
(typearea)  \topskip= 12.0pt
(typearea)  \footskip   = 50.75pt
(typearea)  \baselineskip   = 14.5pt
(typearea)  on input line 1211.
)
\c@part=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\abovecaptionskip=\skip45