Re: “Missing Glyphs!” / LinLibertine

[Jürgen Spitzmüller]

Am Dienstag, den 30.01.2018, 13:09 -0500 schrieb Scott Kostyshak:
> Thank you for your detailed explanations.

+1.

Jürgen

> 
> Scott

signature.asc
Description: This is a digitally signed message part

Re: LyX for linguists

[Jürgen Spitzmüller]

Am Dienstag, den 30.01.2018, 12:00 +0100 schrieb Michael Berger:
> Hallo Jürgen,
> 
> many, many thanks for the huge number of various improvements and 
> continued provision of so many special enhancements when using LyX
> for 
> writing Linguistic Papers. Makes working with LyX so much more
> comfortable!
> 
> Just great!

Thanks, Michael, I am glad to hear that.

Jürgen

> 
> Michael
> 

signature.asc
Description: This is a digitally signed message part

Re: LyX version 2.3.0rc2 available

[Ian Worthington]

 Scott --
Do Windows users on rc1 need to install the full bundle again or will the 
installer suffice?
ian

  

Re: miktex update has no effect

[Ian Worthington]

 Danke Uwe.
Going to the update wizard via the package manager, rather than directly (even 
as admin) seems to fix the problem.
thanks,
Ian
On Tuesday, January 30, 2018, 11:59:39 PM GMT-5, Uwe Stöhr 
 wrote:  
 
 Am 30.01.2018 um 07:31 schrieb Ian Worthington:

 > 1. When I do a miktex update and select packages to update, there is 
activity, and no errors recorded in the log, but when I return to the 
update package list nothing has changed.

This sounds like a problem with the package repository.
An unfinished update explains your second problem.

Therefore please start MiKTeX's update program (the Admin version) via 
the Windows start menu. At first try to run the update normally. If this 
succeeds, please run the update again because for older installations 2 
runs could be necessary.
If the update is still not successful, restart the MiKTeX update and 
select in the welcome page to select another package repository. Then it 
should work. If so, please also run the update a second time until there 
are no more updates found.

regards Uwe
  

LyX version 2.3.0rc2 available

[Scott Kostyshak]

Public release of LyX version 2.3.0rc2


We are proud to announce the second public release candidate of the new LyX 2.3
series. This pre-release is meant for testing and should not be used for
serious work. For curious users who would like to test in order to help catch
bugs before the 2.3.0 release, please back up all of your documents and be
prepared for the worst to happen. Most users (who desire a stable LyX version)
should not use this pre-release.

The 2.3 series has a rich set of new features compared to the current stable
series. An overview of the new features can be found here:

  https://wiki.lyx.org/LyX/NewInLyX23

You can download LyX 2.3.0rc2 from ftp://ftp.lyx.org/pub/lyx/devel/.

We appreciate your help in testing this pre-release!

If a file from an earlier version of LyX is opened *and saved* with
any version of 2.3.x, then the original file will automatically be
backed up. The backup file will be found in the backup directory, if one
is set under Tools> Preferences> Paths, or else in the same folder as
the original file, if no backup directory is set. The filename of the
backup file will be:
ORIGNAME-lyxformat-NUM.lyx~
where NUM is the LyX format number of the original file. In the case of
2.2.x file, this will be 508, but in the case of older files it will be
different.

The file lib/RELEASE-NOTES lists some known issues and problems compared
to the current stable releases (LyX 2.2.x). We strongly recommend that
packagers of LyX on various platforms and distributions read this file.

As with any major release, this one comes with a lot of new features but
also some bugs. If you think you have found a bug in LyX 2.3.0rc2, either
email the LyX developers' mailing list (lyx-devel at lists.lyx.org),
or open a bug report at https://www.lyx.org/trac/wiki/BugTrackerHome.
Please specify if the behavior you are reporting is different from behavior
in a previous LyX version.

If you have trouble using LyX or have a question, consult the
documentation that comes with LyX (under Help) and the LyX wiki, which you
will find at https://wiki.lyx.org/. You can also send email to the LyX users'
list (lyx-users at lists.lyx.org).

The LyX team.
https://www.lyx.org



signature.asc
Description: PGP signature

Re: miktex update has no effect

[Uwe Stöhr]

Am 30.01.2018 um 07:31 schrieb Ian Worthington:

> 1. When I do a miktex update and select packages to update, there is 
activity, and no errors recorded in the log, but when I return to the 
update package list nothing has changed.


This sounds like a problem with the package repository.
An unfinished update explains your second problem.

Therefore please start MiKTeX's update program (the Admin version) via 
the Windows start menu. At first try to run the update normally. If this 
succeeds, please run the update again because for older installations 2 
runs could be necessary.
If the update is still not successful, restart the MiKTeX update and 
select in the welcome page to select another package repository. Then it 
should work. If so, please also run the update a second time until there 
are no more updates found.


regards Uwe

Re: miktex update has no effect

[Uwe Stöhr]

Am 30.01.2018 um 07:31 schrieb Ian Worthington:


I've just installed the lyx 2.3 rc on my windows 10 system.

I have two problems so far:

1. When I do a miktex update and select packages to update, there is 
activity, and no errors recorded in the log, but when I return to the 
update package list nothing has changed.


This sounds like a problem with the package repository.
An unfinished update explains your second problem.

Therefore please start MiKTeX's update program (the Admin version) via 
the Windows start menu. At first try to run the update normally. If this 
succeeds, please run the update again because for older installations 2 
runs could be necessary.
If the update is still not successful, restart the MiKTeX update and 
select in the welcome page to select another package repository. Then it 
should work. If so, please also run the update a second time until there 
are no more updates found.


regards Uwe

Re: miktex update has no effect

[Ian Worthington]

 This is the bundle.
Maybe it's still in the log?  Where do I find that?
Ian
On Tuesday, January 30, 2018, 1:09:29 PM GMT-5, Scott Kostyshak 
 wrote:  
 
 On Tue, Jan 30, 2018 at 06:31:12AM +, Ian Worthington wrote:
> I've just installed the lyx 2.3 rc on my windows 10 system.

Thanks for testing, Ian!

Did you test the bundle or the non-bundle?

> I have two problems so far:
> 1. When I do a miktex update and select packages to update, there is 
> activity, and no errors recorded in the log, but when I return to the update 
> package list nothing has changed.
> 2. The very first time I clicked VIEW on the sample document it gave an error 
> message, which I regret I neglected to make a note of.  It works fine 
> subsequently, but something to be aware of for new users maybe?

That is indeed good to know. I wonder what happened. If you do see that
error again it would be interesting to see the log.

Thanks for your feedback,

Scott
  

Re: Using algorithm2e with Package Options, Recommended Approach?

[Joel Kulesza]

On Tue, Jan 30, 2018 at 4:06 PM, Paul A. Rubin  wrote:
>
> Does the attached module do what you want (or show the way)? I just moved
> all the preamble stuff from your MWE into a hacked version of Jürgen's
> module. Feel free to change the name from "MyAlgorithm2e". Imagination is
> in short supply at the moment.


Paul,

Yes, and thanks for digging into this! My main hangup was thinking that I
needed the PackageOptions and AddToPreamble within the float rather than in
the external "module namespace."

Best regards,
Joel

Re: Using algorithm2e with Package Options, Recommended Approach?

[Paul A. Rubin]

On 01/29/2018 12:28 PM, Joel Kulesza wrote:

Colleagues:

What is the recommended way to \usepackage{algorithm2e} with 
additional options
and potentially other global preamble customizations (ideally also 
allowing

algorithm floats in the LyX GUI)?

For example, I'd like to have in my preamble for algorithm2e:

\usepackage[ruled,vlined,resetcount,algochapter,linesnumbered]{algorithm2e}

and also

    \usepackage{xcolor} % Because of colors called out below.
    \SetArgSty{textnormal}
    \SetNlSty{texttt}{\color{gray}}{}
\newcommand\mycommfont[1]{\footnotesize\ttfamily\textcolor{blue}{#1}}
    \SetCommentSty{mycommfont}
    \DontPrintSemicolon

I cannot see how to customize the existant algorithm2e.module.  At a 
minimum

just to get the package with options, I've tried:

    AddToPreamble
\usepackage[ruled,vlined,resetcount,algochapter,linesnumbered]{algorithm2e}
    EndPreamble

    Preamble
\usepackage[ruled,vlined,resetcount,algochapter,linesnumbered]{algorithm2e}
    EndPreamble

    PackageOptions ruled vlined resetcount algochapter linesnumbered

    PackageOptions algorithm2e ruled vlined resetcount algochapter 
linesnumbered


    PackageOptions "algorithm2e ruled vlined resetcount algochapter 
linesnumbered"


with and without commenting out the line "Requires algorithm2e".  I've 
tried
this with a new .module file with intermittent reconfigures as well as 
Document
Settings -> Local Layout.  However, nothing I try gets the proper line 
inserted

into the document preamble.  I assume this is because I'm defining a float
rather than a text class.

I can include
"\usepackage[ruled,vlined,resetcount,algochapter,linesnumbered]{algorithm2e}" 
in
the document preamble; however, when I Insert -> Float -> Algorithm 
and view the
source, new lines are added to the LyX-generated preamble 
corresponding to the

lines added with the intrinsic LyX algorithm:

    \floatstyle{ruled}
    \newfloat{algorithm}{tbp}{loa}
    \providecommand{\algorithmname}{Algorithm}
    \floatname{algorithm}{\protect\algorithmname}

which results in errors like "Command \algorithm already defined.".  I'm
reluctant to modify the defaults to remove the built-in algorithm 
environment

(perhaps unnecessary reluctance?).

The best solution I've identified is keeping the lines I want in the 
preamble

and not using Insert -> Float -> Algorithm or Insert -> List -> List of
Algorithms but rather inserting child .tex documents with all 
captions, labels,

content within them and \listofalgorithms using ERT. However, this allows
cross-references to get out of sync easily (and forces me to insert 
valid albeit
seemingly broken references via the LyX GUI).  However, hyperlinks 
appear to

work when ultimately rendered.

MWE attached for "the best I've developed."  Hopefully there is a 
better way
that I've overlooked (perhaps redefining algorithm2e.module to 
override the

builtin algorithm but not include any additional preamble content and then
including all my code in the preamble?).

Any thoughts are appreciated to satisfy my wish list of:

* Using package-optioned algorithm2e instead of LyX built-in algorithm and
* Using the LyX GUI to interact with algorithms (at least to do label and
  cross-reference management; keeping the algorithm code external is 
preferred).


Please don't hesitate to contact me with comments, questions, or concerns.

Thank you,
Joel
Does the attached module do what you want (or show the way)? I just 
moved all the preamble stuff from your MWE into a hacked version of 
Jürgen's module. Feel free to change the name from "MyAlgorithm2e". 
Imagination is in short supply at the moment.


Paul

#\DeclareLyXModule[algorithm2e.sty]{MyAlgorithm2e}
#DescriptionBegin
# Use the algorithm2e package for algorithm floats rather
# than LyX's home-brewed algorithm floats.
# Include custom options for the algorithm2e package.
#DescriptionEnd
#
#Author: Jürgen Spitzmüller

Format 60

Requires algorithm2e,xcolor

PackageOptions algorithm2e "ruled,vlined,resetcount,algochapter,linesnumbered"

AddToPreamble
  \SetArgSty{textnormal}
  \SetNlSty{texttt}{\color{gray}}{}
  \newcommand\mycommfont[1]{\footnotesize\ttfamily\textcolor{blue}{#1}}
  \SetCommentSty{mycommfont}
  \DontPrintSemicolon
EndPreamble

Float
Type  algorithm
GuiName   Algorithm
Placement tbp
AllowedPlacement  !htbp
AllowsSideways0
Extension loa
NumberWithin  none
Style plain
ListName  "List of Algorithms"
IsPredefined  true
UsesFloatPkg  false
ListCommand   listofalgorithms
RefPrefix alg
End

Re: LyX for linguists

[Michael Berger]

Thanks Scott, yes I'm aware of that Wiki Page. I should have mentioned 
it to benefit other people  but simply forgot to. BTW, the wiki page we 
are talking about is very informative and exhaustive.


Michael


On 30.01.2018 19:13, Scott Kostyshak wrote:

On Tue, Jan 30, 2018 at 11:00:31AM +, Michael Berger wrote:

Hallo Jürgen,

many, many thanks for the huge number of various improvements and continued
provision of so many special enhancements when using LyX for writing
Linguistic Papers. Makes working with LyX so much more comfortable!

Probably you already know, but just in case, there is a detailed Wiki
page for linguistics with LyX:

   https://wiki.lyx.org/LyX/LinguistLyX

Scott

Re: LyX for linguists

[Scott Kostyshak]

On Tue, Jan 30, 2018 at 11:00:31AM +, Michael Berger wrote:
> Hallo Jürgen,
> 
> many, many thanks for the huge number of various improvements and continued
> provision of so many special enhancements when using LyX for writing
> Linguistic Papers. Makes working with LyX so much more comfortable!

Probably you already know, but just in case, there is a detailed Wiki
page for linguistics with LyX:

  https://wiki.lyx.org/LyX/LinguistLyX

Scott


signature.asc
Description: PGP signature

Re: miktex update has no effect

[Scott Kostyshak]

On Tue, Jan 30, 2018 at 06:31:12AM +, Ian Worthington wrote:
> I've just installed the lyx 2.3 rc on my windows 10 system.

Thanks for testing, Ian!

Did you test the bundle or the non-bundle?

> I have two problems so far:
> 1. When I do a miktex update and select packages to update, there is 
> activity, and no errors recorded in the log, but when I return to the update 
> package list nothing has changed.
> 2. The very first time I clicked VIEW on the sample document it gave an error 
> message, which I regret I neglected to make a note of.  It works fine 
> subsequently, but something to be aware of for new users maybe?

That is indeed good to know. I wonder what happened. If you do see that
error again it would be interesting to see the log.

Thanks for your feedback,

Scott

Re: “Missing Glyphs!” / LinLibertine

[Scott Kostyshak]

On Tue, Jan 30, 2018 at 09:42:14AM +, Guenter Milde wrote:
> On 2018-01-29, Jürgen Spitzmüller wrote:
> > Am Montag, den 29.01.2018, 10:55 +0100 schrieb S. Noble:
> 
> >> Thanks, Scott and Günter, for your quick, helpful replies.
> >> I had followed Scott’s advice and found the offending character. It
> >> was indeed the lower-case Greek letter “sigma”, not in a word-final
> >> position (i.e., “σ”). (There was just one of them in the document).
> >> I was then puzzling over LyX’s error message — “There is no v in font
> >> LinLibertineT-osf-lgr”. 
> 
> > That's not LyX's error message, but LaTeX's (or polyglossia's for that
> > matter).
> 
> While Polyglossia is known for a lot of false positives when checking
> character support, it is not to blame here. Polyglossia tests for script
> support in the used fonts, relying on often missing information in the
> font metadata and gives errors (not just warnings).
> The "There is no … in font …" warnings are from TeX.

Do you think it is worthwhile to report bugs regarding missing
information in the font metadata, or in your experience is it not likely
to lead to fixes? I suppose I would need to find the upstream font
definitions and report them there, for each individual issue?

> ...

Thank you for your detailed explanations.

Scott

Re: Lyx 2.3.0rc2 -- Incorrect saving of file-name in Linux

[F M Salter]

Correction:

    please ignore export comments.  I had finished with two files.  I
confused the one from which I carried out the exporting!

Regards


On 30/01/18 09:49, F M Salter wrote:
> More problems.
>
>     Even when a LyX file has the correct number of dots and is saving
> correctly, export to other output forms loses the part after the dot.
>
>     This can easily lead to the disastrous overwriting of existing files.
>
> Regards
>
> Frank Salter
>
>
> On 30/01/18 09:03, F M Salter wrote:
>> Hi
>>
>>        LyX saves new files with incorrect names when the specified name
>> contains dots as separators.
>>
>>         Example:  Specified file name is  file-2018.Jan.30  expecting
>> .lyx to be added as is usual
>>
>>                      Saved file name is      file-2018.Jan.lyx
>>
>>         If the full name complete with *.lyx is saved, it does so correctly.
>>
>> Regards
>>
>> Frank Salter
>>

LyX for linguists

[Michael Berger]

Hallo Jürgen,

many, many thanks for the huge number of various improvements and 
continued provision of so many special enhancements when using LyX for 
writing Linguistic Papers. Makes working with LyX so much more comfortable!


Just great!

Michael

Re: Lyx 2.3.0rc2 -- Incorrect saving of file-name in Linux

[Jean-Marc Lasgouttes]

Le 30/01/2018 à 10:49, F M Salter a écrit :

More problems.

     Even when a LyX file has the correct number of dots and is saving
correctly, export to other output forms loses the part after the dot.

     This can easily lead to the disastrous overwriting of existing files.


Dear Frank,

I guess there are several places where we are not careful enough. Could 
you open a ticket that outlines the precise steps you use that lead to 
bad behavior?


Thanks,
JMarc



On 30/01/18 09:03, F M Salter wrote:

Hi

        LyX saves new files with incorrect names when the specified name
contains dots as separators.

         Example:  Specified file name is  file-2018.Jan.30  expecting
.lyx to be added as is usual

                      Saved file name is      file-2018.Jan.lyx

         If the full name complete with *.lyx is saved, it does so correctly.

Regards

Frank Salter

Re: Lyx 2.3.0rc2 -- Incorrect saving of file-name in Linux

[F M Salter]

More problems.

    Even when a LyX file has the correct number of dots and is saving
correctly, export to other output forms loses the part after the dot.

    This can easily lead to the disastrous overwriting of existing files.

Regards

Frank Salter


On 30/01/18 09:03, F M Salter wrote:
> Hi
>
>        LyX saves new files with incorrect names when the specified name
> contains dots as separators.
>
>         Example:  Specified file name is  file-2018.Jan.30  expecting
> .lyx to be added as is usual
>
>                      Saved file name is      file-2018.Jan.lyx
>
>         If the full name complete with *.lyx is saved, it does so correctly.
>
> Regards
>
> Frank Salter
>

Re: “Missing Glyphs!” / LinLibertine

[Guenter Milde]

On 2018-01-29, Jürgen Spitzmüller wrote:
> Am Montag, den 29.01.2018, 10:55 +0100 schrieb S. Noble:

>> Thanks, Scott and Günter, for your quick, helpful replies.
>> I had followed Scott’s advice and found the offending character. It
>> was indeed the lower-case Greek letter “sigma”, not in a word-final
>> position (i.e., “σ”). (There was just one of them in the document).
>> I was then puzzling over LyX’s error message — “There is no v in font
>> LinLibertineT-osf-lgr”. 

> That's not LyX's error message, but LaTeX's (or polyglossia's for that
> matter).

While Polyglossia is known for a lot of false positives when checking
character support, it is not to blame here. Polyglossia tests for script
support in the used fonts, relying on often missing information in the
font metadata and gives errors (not just warnings).
The "There is no … in font …" warnings are from TeX.

>> It didn’t seem to make sense, for two reasons: (1) the problem
>> was certainly the letter “sigma”, but in principle it has nothing to
>> do with a “v”; and (2) in the PDF print-out, the letter “sigma” is
>> printed correctly. So, all in all, nothing is missing. I couldn’t
>> figure it out or find anything about it, and then came Günter’s
>> explanation.

The problem is that currently, in LyX's Unicode translation file we use the
Latin transcription for Greek:

In the Latin transcription, "s" stands for "\textautosigma", which
depending on the next characters is printed as "sigma" or "finalsigma".
This is fine if you type Greek text using Latin characters but bad if in
a document you write a single literal "σ" and in the PDF you get a single
"ς". Therefore, LyX uses the "never-to-become-finalsigma" transcript "sv"
with the "LGR ligature break character" "v" (cf.
https://www.lyx.org/trac/ticket/4966):

 0x03c3 "\\textgreek{sv}" "textgreek" 
"force=iso8859-7;cp437;cp437de;cp865,mathalpha" "\\sigma" "" # GREEK SMALL 
LETTER SIGMA

That "v" is missing in Libertine LGR is a bug in this font. May be they call
it a feature, because the effect of a missing character is almost the same
as a "ligature break" character: it prevents ligating (fine) but
* it also triggers a warning
* there is a/no ligature break in the text if you copy-paste from the PDF.

LyX turns warnings about missing characters into errors for good reason.
Unfortunately this can give rise to false positives in rare cases.

We had a similar problem with Unicode fonts lacking the ligature break
character (u200C, ZWNJ). However, we cannot tell LyX to ignore missing
"v" characters (which stand for ZWNJ in the LGR font encoding but are
printable characters normally).

The proper solution is to use the LaTeX internal character representation
(LICR) in the Unicode translation file:

 0x03c3 "\\textgreek{\\textsigma}""textgreek" 
"force=iso8859-7,mathalpha" "\\sigma" "" # GREEK SMALL LETTER SIGMA

A patch is ready since some years but hold back because Greek LICR macros
were a new feature at this time. I believe it is time to apply the patch
now. It works stable on my local installation and fixes the problem + some
others.


>> So at least I’ve understood (sort of), but this is strange behaviour
>> from LyX. LaTeX, on the other hand, doesn’t complain and prints the
>> “sigma” identically.

> You get the message as well, LaTeX is just not aborted (since it's a
> warning, actually).

This depends: If you use literal Greek characters in the LaTeX source, there
is no warning.

A simple workaround in LyX is to set the LaTeX input encoding to UTF-8:

 Document>Settings>Language>Encoding>Other: Unicode (utf8)
 
("Language default" does not work, because we force-convert sigma to
override inputenc's "iso8859-7.def" replacing it with "autosigma".
https://www.lyx.org/trac/ticket/8509)


>> I'm wondering if the problem might be solved by LyX following LaTeX's
>> advice. If, as LaTeX complains, "The libertine-type1 package is
>> obsolete", then perhaps LyX should be using, as
>> LaTeX's suggests, "\usepackage[type1]{libertineRoman}" in the
>> Preamble instead of "\usepackage{libertine-type1}". 

This will not solve the warning issue (the font itself is the same).
Nevertheless, it may be a good idea to update the font call once we can
safely expect users to have the new interface or after a test in the LaTeX
configuration.

...

Günter



Test document:

#LyX 2.2 created this file. For more info see http://www.lyx.org/
\lyxformat 508
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass scrartcl
\begin_preamble
\usepackage[type1]{libertineRoman}
\end_preamble
\use_default_options false
\maintain_unincluded_children false
\language ngerman
\language_package default
\inputencoding utf8
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 

Re: “Missing Glyphs!” / LinLibertine

[Jürgen Spitzmüller]

2018-01-30 9:42 GMT+01:00 S. Noble :

> It’s interesting to hear all that. As nice as the Linux Libertine font is,
> it’s the one that gives me the most issues, such as the one described
> above. I’m sure that the hassles I experience are different from the ones
> you face, but when you say that it’s getting annoying, I fully agree.
>

Never mind, this is just some ranting. It's not too hard to deal with this.

> Again, LyX is fantastic software—keep up the great work!
>

Thank you.

Jürgen


> Seb.
>

Problem: version control suddenly no longer works in LyX 2.2 and 2.3rc1

[Busch, Andreas]

Hi,

for years I have used LyX with version control (GNU rcs) on a number of 
documents which I regularly revise. It has proved very useful for that purpose.

Trying to check out one of these documents I ran into trouble yesterday, 
however. LyX threw up an unexplained error box indicating that trying to use co 
(checkout) had resulted in an error. All other attempts (rolling back the last 
check-in or trying to register a new document with rcs) also failed.

I use GNU RCS 5.9.0 which appears to be the most recent, on a Mac with High 
Sierra (10.13.2) and LyX 2.2. Updating to LyX 2.3rc1 made no difference. I am 
not sure whether the last successful use of rcs with LyX predates upgrading to 
High Sierra, otherwise there were no changes to my setup.

Having checked the mailing list archive, I find no recent discussion of 
problems around rcs. If anyone has an idea where the cause of the error may be 
or any suggestions what else I should try I'd be very grateful!

Thanks and best wishes,

Andreas


signature.asc
Description: Message signed with OpenPGP

Re: “Missing Glyphs!” / LinLibertine

[Ricardo Berlasso]

2018-01-30 9:42 GMT+01:00 S. Noble :

>
> Yes, we can (and will) do that. But it's getting annoying, to be honest.
> This is the fourth time a new package for libertine is released
> and the old one declared obsolete over the last 5 years. We
> had libertine-type1, which was then declared obsolete by libertine
> (or libertine-legacy), which was then declared obsolete by a new
> libertine-type1. Now libertineRoman declares libertine-type1 obsolete. This
> is just crazy.
>
> Jürgen
>
>
> It’s interesting to hear all that. As nice as the Linux Libertine font is,
> it’s the one that gives me the most issues, such as the one described
> above. I’m sure that the hassles I experience are different from the ones
> you face, but when you say that it’s getting annoying, I fully agree.
>

I simply use the OpenType Libertinus fonts (an actively developed fork of
Linux Libertine and Biolinum) with XeTeX

https://github.com/khaledhosny/libertinus

No problem at all.

[If you don't mind the self promotion, I wrote for my personal blog a quick
introduction to the use of OpenType on XeTeX/LyX. This is the first article
of the "miniseries"

https://frommindtotype.wordpress.com/2018/01/15/using-opentype-on-xetexlyx-short-texts/

The fourth and last one will be published next Monday.]

Regards,
Ricardo





> Again, LyX is fantastic software—keep up the great work!
>
> Seb.
>

Lyx 2.3.0rc2 -- Incorrect saving of file-name in Linux

[F M Salter]

Hi

       LyX saves new files with incorrect names when the specified name
contains dots as separators.

        Example:  Specified file name is  file-2018.Jan.30  expecting
.lyx to be added as is usual

                     Saved file name is      file-2018.Jan.lyx

        If the full name complete with *.lyx is saved, it does so correctly.

Regards

Frank Salter

Re: “Missing Glyphs!” / LinLibertine

[S. Noble]

> Yes, we can (and will) do that. But it's getting annoying, to be honest. This 
> is the fourth time a new package for libertine is released  
> and the old one declared obsolete over the last 5 years. We had 
> libertine-type1, which was then declared obsolete by libertine (or 
> libertine-legacy), which was then declared obsolete by a new libertine-type1. 
> Now libertineRoman declares libertine-type1 obsolete. This is just crazy. 
> 
> Jürgen

It's interesting to hear all that. As nice as the Linux Libertine font
is, it's the one that gives me the most issues, such as the one
described above. I'm sure that the hassles I experience are different
from the ones you face, but when you say that it's getting annoying, I
fully agree. 

Again, LyX is fantastic software--keep up the great work! 

Seb.