Re: Interesting for LyX: ShareLaTeX and github

[Guenter Milde]

On 2014-09-18, Rainer M Krug wrote:

>> And, if you have LyX you have enough disk space for a  minimal LaTeX
>> installation, even in Africa :-)-O

Yes, I do have LyX and LaTeX on my OLPC XO-Laptop. It fits also on the Nokia
N800 tablet - actually on any not too old SD-card.

> I agree completely here - but still it makes life easier when one does
> not have to worry about the compilation of the document.

As long as everything goes fine, you will not realize the LaTeX
compilation on your local computer either. And with "cloud" based
compiling, you actually have to worry more at the moment the first error
occures...

Also, I would not send my private mail etc. over the net more than necessary.

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-23, Scott Kostyshak wrote:
 On Wed, Jul 23, 2014 at 5:18 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2014-07-22, Will Parsons wrote:
 I'm writing an article that will contain IPA and various non-Latin
 alphabetic characters in it.  Eveything went well inserting IPA and Greek
 letters into the PDF, but when I tried to add Hebrew letters, I get an
 error when trying to export to PDF:

   Could not find LaTeX command for character 'א' (code point 0x5d0)

 I've tried various possibilities for Language - changing to Unicode
 (utf8) for example yields:

   Package inputenc Error: Unicode char \u8:א not set up for use with LaTeX.

 How do I solve this?

 The easiest way should be to use XeTeX or LuaTeX convertes. In
 DocumentSettingsFonts check use non-TeX fonts and select a font
 containing all required Glyphs (the default Latin Modern fonts don't!).

 Just a note that in my experience XeTeX works well with non-TeX fonts
 and LuaTeX does not work at all.

My experience is, that both XeTeX and LuaTeX work. However, LuaTeX is
newer but XeTeX is unmaintained so on older systems XeTeX might be the
better choice while on new or recently updated systems LuaTeX migt be better.

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-23, Will Parsons wrote:
 Guenter Milde wrote:
 On 2014-07-22, Will Parsons wrote:

 Thanks - this looks promising.  I'll just have to find out what fonts
 support all my characters.  Is there a good way to do that short of
 trying them one-by-one?

As non-TeX fonts == system fonts, there is a wide choice:

You may use a font preview program (which, depends on your OS and other
preferences).

Alternatively, you may use a WYSIWYG text processor and try a paragraph
with Latin, Greek and Hebrew in different system fonts.

DejaVu and Linux Libertine are fonts that are known to support a wide range
of characters.

 Otherwise:
 Are Hebrew 8-bit TeX fonts and the TeX support for Hebrew installed?

 Excuse my ignorance, but how do I determine that?

This depends on your setup. You may look for the presence of hebrew.ldf
or a similar Babel language file in your system. On Debian, a package like
texlive-language-hebrew (or similar) may be installed or not installed.

In lyx, you can search the document under HelpLaTeX configuration
for a line like

  Your LaTeX installation has hyphenation patterns for the following languages:

and see if hebrew is listed in the following lines.

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-23, Scott Kostyshak wrote:
 On Wed, Jul 23, 2014 at 5:18 AM, Guenter Milde mi...@users.sf.net wrote:
 On 2014-07-22, Will Parsons wrote:
 I'm writing an article that will contain IPA and various non-Latin
 alphabetic characters in it.  Eveything went well inserting IPA and Greek
 letters into the PDF, but when I tried to add Hebrew letters, I get an
 error when trying to export to PDF:

   Could not find LaTeX command for character 'א' (code point 0x5d0)

 I've tried various possibilities for Language - changing to Unicode
 (utf8) for example yields:

   Package inputenc Error: Unicode char \u8:א not set up for use with LaTeX.

 How do I solve this?

 The easiest way should be to use XeTeX or LuaTeX convertes. In
 DocumentSettingsFonts check use non-TeX fonts and select a font
 containing all required Glyphs (the default Latin Modern fonts don't!).

 Just a note that in my experience XeTeX works well with non-TeX fonts
 and LuaTeX does not work at all.

My experience is, that both XeTeX and LuaTeX work. However, LuaTeX is
newer but XeTeX is unmaintained so on older systems XeTeX might be the
better choice while on new or recently updated systems LuaTeX migt be better.

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-23, Will Parsons wrote:
 Guenter Milde wrote:
 On 2014-07-22, Will Parsons wrote:

 Thanks - this looks promising.  I'll just have to find out what fonts
 support all my characters.  Is there a good way to do that short of
 trying them one-by-one?

As non-TeX fonts == system fonts, there is a wide choice:

You may use a font preview program (which, depends on your OS and other
preferences).

Alternatively, you may use a WYSIWYG text processor and try a paragraph
with Latin, Greek and Hebrew in different system fonts.

DejaVu and Linux Libertine are fonts that are known to support a wide range
of characters.

 Otherwise:
 Are Hebrew 8-bit TeX fonts and the TeX support for Hebrew installed?

 Excuse my ignorance, but how do I determine that?

This depends on your setup. You may look for the presence of hebrew.ldf
or a similar Babel language file in your system. On Debian, a package like
texlive-language-hebrew (or similar) may be installed or not installed.

In lyx, you can search the document under HelpLaTeX configuration
for a line like

  Your LaTeX installation has hyphenation patterns for the following languages:

and see if hebrew is listed in the following lines.

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-23, Scott Kostyshak wrote:
> On Wed, Jul 23, 2014 at 5:18 AM, Guenter Milde <mi...@users.sf.net> wrote:
>> On 2014-07-22, Will Parsons wrote:
>>> I'm writing an article that will contain IPA and various non-Latin
>>> alphabetic characters in it.  Eveything went well inserting IPA and Greek
>>> letters into the PDF, but when I tried to add Hebrew letters, I get an
>>> error when trying to export to PDF:

>>>   Could not find LaTeX command for character 'א' (code point 0x5d0)

>>> I've tried various possibilities for Language - changing to "Unicode
>>> (utf8)" for example yields:

>>>   Package inputenc Error: Unicode char \u8:א not set up for use with LaTeX.

>>> How do I solve this?

>> The easiest way should be to use XeTeX or LuaTeX convertes. In
>> Document>Settings>Fonts check "use non-TeX fonts" and select a font
>> containing all required Glyphs (the default Latin Modern fonts don't!).

> Just a note that in my experience XeTeX works well with non-TeX fonts
> and LuaTeX does not work at all.

My experience is, that both XeTeX and LuaTeX work. However, LuaTeX is
newer but XeTeX is unmaintained so on older systems XeTeX might be the
better choice while on new or recently updated systems LuaTeX migt be better.

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-23, Will Parsons wrote:
> Guenter Milde wrote:
>> On 2014-07-22, Will Parsons wrote:

> Thanks - this looks promising.  I'll just have to find out what fonts
> support all my characters.  Is there a good way to do that short of
> trying them one-by-one?

As non-TeX fonts == system fonts, there is a wide choice:

You may use a font preview program (which, depends on your OS and other
preferences).

Alternatively, you may use a WYSIWYG "text processor" and try a paragraph
with Latin, Greek and Hebrew in different system fonts.

DejaVu and Linux Libertine are fonts that are known to support a wide range
of characters.

>> Otherwise:
>> Are Hebrew 8-bit TeX fonts and the TeX support for Hebrew installed?

> Excuse my ignorance, but how do I determine that?

This depends on your setup. You may look for the presence of hebrew.ldf
or a similar Babel language file in your system. On Debian, a package like
texlive-language-hebrew (or similar) may be installed or not installed.

In lyx, you can search the document under Help>LaTeX configuration
for a line like

  Your LaTeX installation has hyphenation patterns for the following languages:

and see if hebrew is listed in the following lines.

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-22, Will Parsons wrote:
 I'm writing an article that will contain IPA and various non-Latin
 alphabetic characters in it.  Eveything went well inserting IPA and Greek
 letters into the PDF, but when I tried to add Hebrew letters, I get an
 error when trying to export to PDF:

   Could not find LaTeX command for character 'א' (code point 0x5d0)

 I've tried various possibilities for Language - changing to Unicode
 (utf8) for example yields:

   Package inputenc Error: Unicode char \u8:א not set up for use with LaTeX.

 How do I solve this?

The easiest way should be to use XeTeX or LuaTeX convertes. In
DocumentSettingsFonts check use non-TeX fonts and select a font
containing all required Glyphs (the default Latin Modern fonts don't!).

Otherwise:
Are Hebrew 8-bit TeX fonts and the TeX support for Hebrew installed?

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-22, Will Parsons wrote:
 I'm writing an article that will contain IPA and various non-Latin
 alphabetic characters in it.  Eveything went well inserting IPA and Greek
 letters into the PDF, but when I tried to add Hebrew letters, I get an
 error when trying to export to PDF:

   Could not find LaTeX command for character 'א' (code point 0x5d0)

 I've tried various possibilities for Language - changing to Unicode
 (utf8) for example yields:

   Package inputenc Error: Unicode char \u8:א not set up for use with LaTeX.

 How do I solve this?

The easiest way should be to use XeTeX or LuaTeX convertes. In
DocumentSettingsFonts check use non-TeX fonts and select a font
containing all required Glyphs (the default Latin Modern fonts don't!).

Otherwise:
Are Hebrew 8-bit TeX fonts and the TeX support for Hebrew installed?

Günter

Re: problem getting non-Latin symbols in PDF

[Guenter Milde]

On 2014-07-22, Will Parsons wrote:
> I'm writing an article that will contain IPA and various non-Latin
> alphabetic characters in it.  Eveything went well inserting IPA and Greek
> letters into the PDF, but when I tried to add Hebrew letters, I get an
> error when trying to export to PDF:

>   Could not find LaTeX command for character 'א' (code point 0x5d0)

> I've tried various possibilities for Language - changing to "Unicode
> (utf8)" for example yields:

>   Package inputenc Error: Unicode char \u8:א not set up for use with LaTeX.

> How do I solve this?

The easiest way should be to use XeTeX or LuaTeX convertes. In
Document>Settings>Fonts check "use non-TeX fonts" and select a font
containing all required Glyphs (the default Latin Modern fonts don't!).

Otherwise:
Are Hebrew 8-bit TeX fonts and the TeX support for Hebrew installed?

Günter

Re: svg graphic import in Lyx

[Guenter Milde]

On 2014-07-12, Wolfgang Engelmann wrote:
 Hello,
 a svg graphic can apparently be imported into a Lyx document. However, 
 it seems it is converted into bitmap if exported eg by pdflatex. Is that 
 true?

This depends on the installed converters. With e.g. inkscape installed, it
is converted to pdf. Bitmap is the fallback.

You may have a look at the configuration log.
More detail about SVG images in LyX should be available in the wiki.

Günter

Re: svg graphic import in Lyx

[Guenter Milde]

On 2014-07-12, Wolfgang Engelmann wrote:
 Hello,
 a svg graphic can apparently be imported into a Lyx document. However, 
 it seems it is converted into bitmap if exported eg by pdflatex. Is that 
 true?

This depends on the installed converters. With e.g. inkscape installed, it
is converted to pdf. Bitmap is the fallback.

You may have a look at the configuration log.
More detail about SVG images in LyX should be available in the wiki.

Günter

Re: svg graphic import in Lyx

[Guenter Milde]

On 2014-07-12, Wolfgang Engelmann wrote:
> Hello,
> a svg graphic can apparently be imported into a Lyx document. However, 
> it seems it is converted into bitmap if exported eg by pdflatex. Is that 
> true?

This depends on the installed converters. With e.g. inkscape installed, it
is converted to pdf. Bitmap is the fallback.

You may have a look at the configuration log.
More detail about SVG images in LyX should be available in the wiki.

Günter

Re: Greek and degree-sign characters in listing

[Guenter Milde]

On 2014-07-01, Alexander Berg wrote:
 Dear all,

 i am using Lyx 2.1.0 on Arch Linux x86 and i hope that somebody out 
 there can help me :). Google told me nothing helpful.

 I am trying to export a document (class: article) to pdf. There are some 
 listings with greek characters and degree signs the appendix of this 
 document. ( Insert-Program Listing, Insert-File(plain text) )

The Listings package and Greek characters are known to be tricky:

It is already nontrivial to have mixed Greek and Latin text characters in
8-bit TeX (e.g. pdftex). This is, because in LaTeX, Greek fonts use a
non-standard Greek-only font encoding.

With LaTeX input encoding set to utf-8 and the package textalpha, you can
get Greek characters in normal Latin Text.

Do Greek text characters work in normal text in your document?

Listings does not handle utf-8: 

   Similarly, if you are using UTF-8 extended characters in a listing,
   they must be placed within an escape to L A TEX.
   
   -- listings.pdf

 If i try to export this document via pdflatex it tells me that there is 
 no representation for these characters in the current encoding. 

What is your encoding?

 After confirming with 'OK' the export gets done and all mentioned
 characters are missing.

There should be an error report/log telling more about what went wrong.

 Using LuaTeX or XeTeX there are no dialogs, but some Error ... UTF-16 
 ... are displayed in the status line for a second. Afterthe export is 
 done the greek characters are missing and the degree-sign is represented 
 as an 'ř'.

 What i am doing wrong and how can i fix it?

Also with LuaTeX/XeTeX, the listings package needs special care. Have a look
at its documentation.

If you insert plain text, make sure the encoding matches what you set in 
DocumentSettingsLanguageEncoding.

Günter

Re: Greek and degree-sign characters in listing

[Guenter Milde]

On 2014-07-01, Alexander Berg wrote:
 Dear all,

 i am using Lyx 2.1.0 on Arch Linux x86 and i hope that somebody out 
 there can help me :). Google told me nothing helpful.

 I am trying to export a document (class: article) to pdf. There are some 
 listings with greek characters and degree signs the appendix of this 
 document. ( Insert-Program Listing, Insert-File(plain text) )

The Listings package and Greek characters are known to be tricky:

It is already nontrivial to have mixed Greek and Latin text characters in
8-bit TeX (e.g. pdftex). This is, because in LaTeX, Greek fonts use a
non-standard Greek-only font encoding.

With LaTeX input encoding set to utf-8 and the package textalpha, you can
get Greek characters in normal Latin Text.

Do Greek text characters work in normal text in your document?

Listings does not handle utf-8: 

   Similarly, if you are using UTF-8 extended characters in a listing,
   they must be placed within an escape to L A TEX.
   
   -- listings.pdf

 If i try to export this document via pdflatex it tells me that there is 
 no representation for these characters in the current encoding. 

What is your encoding?

 After confirming with 'OK' the export gets done and all mentioned
 characters are missing.

There should be an error report/log telling more about what went wrong.

 Using LuaTeX or XeTeX there are no dialogs, but some Error ... UTF-16 
 ... are displayed in the status line for a second. Afterthe export is 
 done the greek characters are missing and the degree-sign is represented 
 as an 'ř'.

 What i am doing wrong and how can i fix it?

Also with LuaTeX/XeTeX, the listings package needs special care. Have a look
at its documentation.

If you insert plain text, make sure the encoding matches what you set in 
DocumentSettingsLanguageEncoding.

Günter

Re: Greek and degree-sign characters in listing

[Guenter Milde]

On 2014-07-01, Alexander Berg wrote:
> Dear all,

> i am using Lyx 2.1.0 on Arch Linux x86 and i hope that somebody out 
> there can help me :). Google told me nothing helpful.

> I am trying to export a document (class: article) to pdf. There are some 
> listings with greek characters and degree signs the appendix of this 
> document. ( Insert->Program Listing, Insert->File(plain text) )

The "Listings" package and Greek characters are known to be tricky:

It is already nontrivial to have mixed Greek and Latin text characters in
8-bit TeX (e.g. pdftex). This is, because in LaTeX, Greek fonts use a
non-standard Greek-only font encoding.

With LaTeX input encoding set to utf-8 and the package "textalpha", you can
get Greek characters in "normal" Latin Text.

Do Greek text characters work in "normal" text in your document?

Listings does not handle utf-8: 

   Similarly, if you are using UTF-8 extended characters in a listing,
   they must be placed within an escape to L A TEX.
   
   -- listings.pdf

> If i try to export this document via pdflatex it tells me that there is 
> no representation for these characters in the current encoding. 

What is your encoding?

> After confirming with 'OK' the export gets done and all mentioned
> characters are missing.

There should be an error report/log telling more about what went wrong.

> Using LuaTeX or XeTeX there are no dialogs, but some "Error ... UTF-16 
> ..." are displayed in the status line for a second. Afterthe export is 
> done the greek characters are missing and the degree-sign is represented 
> as an 'ř'.

> What i am doing wrong and how can i fix it?

Also with LuaTeX/XeTeX, the listings package needs special care. Have a look
at its documentation.

If you insert plain text, make sure the encoding matches what you set in 
Document>Settings>Language>Encoding.

Günter

Re: Unsupported math environments

[Guenter Milde]

On 2014-06-30, Jacob Bishop wrote:
 On Sun, Jun 29, 2014 at 1:52 AM, Georg Baum georg.b...@post.rwth-aachen.de
 wrote:


 Unfortunately it is not possible to use unsupported math environments
 in LyX without putting the whole formula in ERT or do some advanced
 macro tricks. 

This depends 

* on the type of math environment:

  It is possible to write \begin{foo}  \end{foo}, 
  
  it is possible to write \begin{foo}{c}  \end{foo} where the second
  opening bracket needs to be input as `Ctrl-l {`,
  
  but I did not find a way to write unescaped `` and `\` in math-mode.
  
* on the notation of advanced:

  if there is a compatible (in input requirements) math environment that
  LyX supports and that is not used in the document, a simple
  re-definition in the user-preable would do the trick.

 The reason for this is that the native LyX format for
 math formulas is LaTeX. This is implemented in such a way that
 _everything_ is parsed, so it is not possible to have a true ERT in
 mathed. The parser supports unknown commands somewhat (so they appear
 in red), but not environments.

 This is of course a problem and needs to be fixed, but up to now nobody
 worked on it. If it does not exist already please file a bug report at
 http://www.lyx.org/trac/wiki/BugTrackerHome to support unknown
 environments
 in math.

 I fully agree with Georg that it is not currently possible to use
 unsupported math environments in LyX without using ERT or macro tricks.
 I also agree that this is a problem that should be fixed (although I
 can't immediately think of an easy way to fix it)

As defining an array/multiline type of equation for LyX is a nontrivial
task, there will be no easy way. I can imagine several ways:

* simple hack: ERT for math: allow unescaped special characters like \ and 
  this would still provide a LyX-rendering for the normal content of the
  unsupported environment.

* Define math environments in LyX-layout rules instead of hard-coded. Then,
  a LyX-module can add support for new math environments.

* math-macro with inheritance: base math macros on existing commands and
  environments, allowing to change name and maybe some more aspects.
  
Günter  

Re: Unsupported math environments

[Guenter Milde]

On 2014-06-30, Jacob Bishop wrote:
 On Sun, Jun 29, 2014 at 1:52 AM, Georg Baum georg.b...@post.rwth-aachen.de
 wrote:


 Unfortunately it is not possible to use unsupported math environments
 in LyX without putting the whole formula in ERT or do some advanced
 macro tricks. 

This depends 

* on the type of math environment:

  It is possible to write \begin{foo}  \end{foo}, 
  
  it is possible to write \begin{foo}{c}  \end{foo} where the second
  opening bracket needs to be input as `Ctrl-l {`,
  
  but I did not find a way to write unescaped `` and `\` in math-mode.
  
* on the notation of advanced:

  if there is a compatible (in input requirements) math environment that
  LyX supports and that is not used in the document, a simple
  re-definition in the user-preable would do the trick.

 The reason for this is that the native LyX format for
 math formulas is LaTeX. This is implemented in such a way that
 _everything_ is parsed, so it is not possible to have a true ERT in
 mathed. The parser supports unknown commands somewhat (so they appear
 in red), but not environments.

 This is of course a problem and needs to be fixed, but up to now nobody
 worked on it. If it does not exist already please file a bug report at
 http://www.lyx.org/trac/wiki/BugTrackerHome to support unknown
 environments
 in math.

 I fully agree with Georg that it is not currently possible to use
 unsupported math environments in LyX without using ERT or macro tricks.
 I also agree that this is a problem that should be fixed (although I
 can't immediately think of an easy way to fix it)

As defining an array/multiline type of equation for LyX is a nontrivial
task, there will be no easy way. I can imagine several ways:

* simple hack: ERT for math: allow unescaped special characters like \ and 
  this would still provide a LyX-rendering for the normal content of the
  unsupported environment.

* Define math environments in LyX-layout rules instead of hard-coded. Then,
  a LyX-module can add support for new math environments.

* math-macro with inheritance: base math macros on existing commands and
  environments, allowing to change name and maybe some more aspects.
  
Günter  

Re: Unsupported math environments

[Guenter Milde]

On 2014-06-30, Jacob Bishop wrote:
> On Sun, Jun 29, 2014 at 1:52 AM, Georg Baum 
> wrote:


>> Unfortunately it is not possible to use unsupported math environments
>> in LyX without putting the whole formula in ERT or do some advanced
>> macro tricks. 

This depends 

* on the type of math environment:

  It is possible to write \begin{foo}  \end{foo}, 
  
  it is possible to write \begin{foo}{c}  \end{foo} where the second
  opening bracket needs to be input as `Ctrl-l {`,
  
  but I did not find a way to write unescaped `&` and `\` in math-mode.
  
* on the notation of "advanced":

  if there is a compatible (in input requirements) math environment that
  LyX supports and that is not used in the document, a simple
  re-definition in the user-preable would do the trick.

>> The reason for this is that the native LyX format for
>> math formulas is LaTeX. This is implemented in such a way that
>> _everything_ is parsed, so it is not possible to have a true ERT in
>> mathed. The parser supports unknown commands somewhat (so they appear
>> in red), but not environments.

>> This is of course a problem and needs to be fixed, but up to now nobody
>> worked on it. If it does not exist already please file a bug report at
>> http://www.lyx.org/trac/wiki/BugTrackerHome to support unknown
>> environments
>> in math.

> I fully agree with Georg that it is not currently possible to use
> unsupported math environments in LyX without using ERT or macro tricks.
> I also agree that this is a problem that should be fixed (although I
> can't immediately think of an easy way to fix it)

As defining an array/multiline type of equation for LyX is a nontrivial
task, there will be no easy way. I can imagine several ways:

* simple hack: ERT for math: allow unescaped special characters like \ and &
  this would still provide a LyX-rendering for the "normal" content of the
  unsupported environment.

* Define math environments in LyX-layout rules instead of hard-coded. Then,
  a LyX-module can add support for new math environments.

* math-macro with "inheritance": base math macros on existing commands and
  environments, allowing to change name and maybe some more aspects.
  
Günter  

Re: paper accepted for publication, but need help!

[Guenter Milde]

On 2014-06-10, Jean-Marc Lasgouttes wrote:
 10/06/2014 13:49, Neal Becker:

 The problem is triggered by my .bib entry, which includes a non-ascii
 character:

author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

 By playing with lyx Document/Settings/Encoding, selecting unicode
 XeTeX (utf-8), I seem to be able to export dvi and then convert dvipdf
 OK.

 So is this a good procedure, or is something else recommended here?

 You should use the same encoding for your document and the LyX output 
 encoding. A workaround is to use LaTeX markup in the .bib file so that 
 it is compatible with any encoding.

I would recommend LaTeX markup (the LICR encoding) as the most stable and
save way to represent non-ASCII characters in a *.bib file.

In the above case, it would be Karol .{Z}yczkowski. 

Some BibTeX-Managers allow to determine the encoding of the bib file and
will do the conversion for you.

Also LyX (usually)¹ does a good job in converting Unicode to the TeX LICR
encoding when you select DocumentSettingsLanguageEncoding: ASCII
Then you can paste/write offending entries into the main window and see
the translation in ViewSourceLaTeX.

Günter


¹ Don't use the LyX translation for Greek and Cyrillic script, as this does
  not use LICR but hard-coded slots in a TeX font encoding. (I am working on
  a patch.)

Re: paper accepted for publication, but need help!

[Guenter Milde]

On 2014-06-10, Jean-Marc Lasgouttes wrote:
 10/06/2014 13:49, Neal Becker:

 The problem is triggered by my .bib entry, which includes a non-ascii
 character:

author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

 By playing with lyx Document/Settings/Encoding, selecting unicode
 XeTeX (utf-8), I seem to be able to export dvi and then convert dvipdf
 OK.

 So is this a good procedure, or is something else recommended here?

 You should use the same encoding for your document and the LyX output 
 encoding. A workaround is to use LaTeX markup in the .bib file so that 
 it is compatible with any encoding.

I would recommend LaTeX markup (the LICR encoding) as the most stable and
save way to represent non-ASCII characters in a *.bib file.

In the above case, it would be Karol .{Z}yczkowski. 

Some BibTeX-Managers allow to determine the encoding of the bib file and
will do the conversion for you.

Also LyX (usually)¹ does a good job in converting Unicode to the TeX LICR
encoding when you select DocumentSettingsLanguageEncoding: ASCII
Then you can paste/write offending entries into the main window and see
the translation in ViewSourceLaTeX.

Günter


¹ Don't use the LyX translation for Greek and Cyrillic script, as this does
  not use LICR but hard-coded slots in a TeX font encoding. (I am working on
  a patch.)

Re: paper accepted for publication, but need help!

[Guenter Milde]

On 2014-06-10, Jean-Marc Lasgouttes wrote:
> 10/06/2014 13:49, Neal Becker:

>> The problem is triggered by my .bib entry, which includes a non-ascii
>> character:

>>author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

>> By playing with lyx Document/Settings/Encoding, selecting unicode
>> XeTeX (utf-8), I seem to be able to export dvi and then convert dvipdf
>> OK.

>> So is this a "good" procedure, or is something else recommended here?

> You should use the same encoding for your document and the LyX output 
> encoding. A workaround is to use LaTeX markup in the .bib file so that 
> it is compatible with any encoding.

I would recommend LaTeX markup (the "LICR encoding") as the most stable and
save way to represent non-ASCII characters in a *.bib file.

In the above case, it would be "Karol .{Z}yczkowski". 

Some BibTeX-Managers allow to determine the encoding of the bib file and
will do the conversion for you.

Also LyX (usually)¹ does a good job in converting Unicode to the TeX "LICR
encoding" when you select Document>Settings>Language>Encoding: ASCII
Then you can paste/write "offending" entries into the main window and see
the translation in View>Source>LaTeX.

Günter


¹ Don't use the LyX translation for Greek and Cyrillic script, as this does
  not use LICR but hard-coded slots in a TeX font encoding. (I am working on
  a patch.)

Re: How to tell LyX to add empty line after paragraphs of my style?

[Guenter Milde]

On 2014-05-17, Enrico Forestieri wrote:
 Roman Inflianskas writes:

 Thank you, it works and looks better, than -separator-.

 Just for information. This issue is solved for the next major release (2.2).
 To achieve your goal you can either simply hit return after an environment
 or use a local layout with NextNoIndent set to false, as you already did
 (but now it will work).

Thanks a lot. This solves a long standing problem.

How is the visual feedback? (For display maths, the presence of white space
around it is almost invisible in the LyX window while it has a profound
effect in the output.)

Günter

Re: How to tell LyX to add empty line after paragraphs of my style?

[Guenter Milde]

On 2014-05-17, Enrico Forestieri wrote:
 Roman Inflianskas writes:

 Thank you, it works and looks better, than -separator-.

 Just for information. This issue is solved for the next major release (2.2).
 To achieve your goal you can either simply hit return after an environment
 or use a local layout with NextNoIndent set to false, as you already did
 (but now it will work).

Thanks a lot. This solves a long standing problem.

How is the visual feedback? (For display maths, the presence of white space
around it is almost invisible in the LyX window while it has a profound
effect in the output.)

Günter

Re: How to tell LyX to add empty line after paragraphs of my style?

[Guenter Milde]

On 2014-05-17, Enrico Forestieri wrote:
> Roman Inflianskas writes:

>> Thank you, it works and looks better, than -separator-.

> Just for information. This issue is solved for the next major release (2.2).
> To achieve your goal you can either simply hit  after an environment
> or use a local layout with NextNoIndent set to false, as you already did
> (but now it will work).

Thanks a lot. This solves a long standing problem.

How is the visual feedback? (For display maths, the presence of white space
around it is almost invisible in the LyX window while it has a profound
effect in the output.)

Günter

Re: is it possible to create a lyx file as flat ASCII file?

[Guenter Milde]

On 2014-05-10, Thirsty Camel wrote:

 [-- Type: text/plain, Encoding:  --]

 Hey, that is new for me. Thanks a lot, I will have a look

 Still, if anyone can tell me if the lyx-file format has any hidden data or
 quirks that would be most welcome. If I know I can create lyx files without
 using lyx (e.g. emacs or python), that would be very useful.

This is definitely possible, see the example below.

While testing, I found out a possible reason for your failure: in the
first run I forgot to use a raw string in Python (i.e. the prefix
operator r in rhello ...). Then, all backslashes (which are used
extensively in LyX's file format have to be escaped.

In Python you must write either

  \\fontencoding
  
or 

  r\fontencoding
  
Otherwise the \f is interpreted as form feed.


Hope this helps,

Günter



#!/usr/bin/env python
# -*- coding: utf8 -*-
# :Copyright: © 2014 Günter Milde.
# Released without warranty under the terms of the
# GNU General Public License (v. 2 or later)

outfile = open(test-out.lyx, w)

outfile.write(r
#LyX 2.0 created this file. For more info see http://www.lyx.org/
\lyxformat 413
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language british
\language_package default
\inputencoding utf8
\fontencoding global
\font_roman lmodern
\font_sans lmss
\font_typewriter lmtt
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100

\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref true
\pdf_bookmarks true
\pdf_bookmarksnumbered false
\pdf_bookmarksopen false
\pdf_bookmarksopenlevel 1
\pdf_breaklinks false
\pdf_pdfborder true
\pdf_colorlinks true
\pdf_backref section
\pdf_pdfusetitle true
\papersize a4paper
\use_geometry false
\use_amsmath 1
\use_esint 1
\use_mhchem 1
\use_mathdots 1
\cite_engine basic
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\use_refstyle 0
\index Stichwortverzeichnis
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Standard
Hello world.
\end_layout

\end_body
\end_document
)

outfile.close()
 

Re: is it possible to create a lyx file as flat ASCII file?

[Guenter Milde]

On 2014-05-10, Thirsty Camel wrote:

 [-- Type: text/plain, Encoding:  --]

 Hey, that is new for me. Thanks a lot, I will have a look

 Still, if anyone can tell me if the lyx-file format has any hidden data or
 quirks that would be most welcome. If I know I can create lyx files without
 using lyx (e.g. emacs or python), that would be very useful.

This is definitely possible, see the example below.

While testing, I found out a possible reason for your failure: in the
first run I forgot to use a raw string in Python (i.e. the prefix
operator r in rhello ...). Then, all backslashes (which are used
extensively in LyX's file format have to be escaped.

In Python you must write either

  \\fontencoding
  
or 

  r\fontencoding
  
Otherwise the \f is interpreted as form feed.


Hope this helps,

Günter



#!/usr/bin/env python
# -*- coding: utf8 -*-
# :Copyright: © 2014 Günter Milde.
# Released without warranty under the terms of the
# GNU General Public License (v. 2 or later)

outfile = open(test-out.lyx, w)

outfile.write(r
#LyX 2.0 created this file. For more info see http://www.lyx.org/
\lyxformat 413
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language british
\language_package default
\inputencoding utf8
\fontencoding global
\font_roman lmodern
\font_sans lmss
\font_typewriter lmtt
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100

\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref true
\pdf_bookmarks true
\pdf_bookmarksnumbered false
\pdf_bookmarksopen false
\pdf_bookmarksopenlevel 1
\pdf_breaklinks false
\pdf_pdfborder true
\pdf_colorlinks true
\pdf_backref section
\pdf_pdfusetitle true
\papersize a4paper
\use_geometry false
\use_amsmath 1
\use_esint 1
\use_mhchem 1
\use_mathdots 1
\cite_engine basic
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\use_refstyle 0
\index Stichwortverzeichnis
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Standard
Hello world.
\end_layout

\end_body
\end_document
)

outfile.close()
 

Re: is it possible to create a lyx file as flat ASCII file?

[Guenter Milde]

On 2014-05-10, Thirsty Camel wrote:

> [-- Type: text/plain, Encoding:  --]

> Hey, that is new for me. Thanks a lot, I will have a look

> Still, if anyone can tell me if the lyx-file format has any hidden data or
> quirks that would be most welcome. If I know I can create lyx files without
> using lyx (e.g. emacs or python), that would be very useful.

This is definitely possible, see the example below.

While testing, I found out a possible reason for your failure: in the
first run I forgot to use a raw string in Python (i.e. the prefix
operator r in r"hello ..."). Then, all backslashes (which are used
extensively in LyX's file format have to be escaped.

In Python you must write either

  "\\fontencoding"
  
or 

  r"\fontencoding"
  
Otherwise the \f is interpreted as form feed.


Hope this helps,

Günter



#!/usr/bin/env python
# -*- coding: utf8 -*-
# :Copyright: © 2014 Günter Milde.
# Released without warranty under the terms of the
# GNU General Public License (v. 2 or later)

outfile = open("test-out.lyx", "w")

outfile.write(r"""
#LyX 2.0 created this file. For more info see http://www.lyx.org/
\lyxformat 413
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language british
\language_package default
\inputencoding utf8
\fontencoding global
\font_roman lmodern
\font_sans lmss
\font_typewriter lmtt
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100

\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref true
\pdf_bookmarks true
\pdf_bookmarksnumbered false
\pdf_bookmarksopen false
\pdf_bookmarksopenlevel 1
\pdf_breaklinks false
\pdf_pdfborder true
\pdf_colorlinks true
\pdf_backref section
\pdf_pdfusetitle true
\papersize a4paper
\use_geometry false
\use_amsmath 1
\use_esint 1
\use_mhchem 1
\use_mathdots 1
\cite_engine basic
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\use_refstyle 0
\index Stichwortverzeichnis
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Standard
Hello world.
\end_layout

\end_body
\end_document
""")

outfile.close()
 

Re: blindtext, unicode-math, and babel won't play nice because of setmathfont

[Guenter Milde]

On 2014-05-10, asllearner wrote:
 This I knew not. But, you are quite correct, it works charmingly.

 (specifically, in the language package custom  
 area:\usepackage{polyglossia}, and in preamble:  
 \setdefaultlanguage{english} )

Then, you can also do this a more LyXish way:

 * DocumentSettingsFonts  [x] use non-TeX fonts
 * DocumentSettingsLanguage language-package [auto]  (or polyglossia)
 * DocumentSettingsLanguage English
 
Günter

Re: is it possible to create a lyx file as flat ASCII file?

[Guenter Milde]

On 2014-05-10, Thirsty Camel wrote:

 Hmm, I spent quite a lot of time doing that without much success even with
 very simple files. Is there anyone who has working tried and made it work?

 Is it necessary to copy the complete header of lyx files - is there a
 minimum header and footer?

I don't know the absolute minimum, but I woudl use LyX to create a
template (empty document or some dummy content or to-be-customized
content) and then use this as a base for the script-generated LyX-file.

Günter

Re: blindtext, unicode-math, and babel won't play nice because of setmathfont

[Guenter Milde]

On 2014-05-10, asllearner wrote:
 This I knew not. But, you are quite correct, it works charmingly.

 (specifically, in the language package custom  
 area:\usepackage{polyglossia}, and in preamble:  
 \setdefaultlanguage{english} )

Then, you can also do this a more LyXish way:

 * DocumentSettingsFonts  [x] use non-TeX fonts
 * DocumentSettingsLanguage language-package [auto]  (or polyglossia)
 * DocumentSettingsLanguage English
 
Günter

Re: is it possible to create a lyx file as flat ASCII file?

[Guenter Milde]

On 2014-05-10, Thirsty Camel wrote:

 Hmm, I spent quite a lot of time doing that without much success even with
 very simple files. Is there anyone who has working tried and made it work?

 Is it necessary to copy the complete header of lyx files - is there a
 minimum header and footer?

I don't know the absolute minimum, but I woudl use LyX to create a
template (empty document or some dummy content or to-be-customized
content) and then use this as a base for the script-generated LyX-file.

Günter

Re: blindtext, unicode-math, and babel won't play nice because of setmathfont

[Guenter Milde]

On 2014-05-10, asllearner wrote:
> This I knew not. But, you are quite correct, it works charmingly.

> (specifically, in the language package custom  
> area:\usepackage{polyglossia}, and in preamble:  
> \setdefaultlanguage{english} )

Then, you can also do this a more "LyXish" way:

 * Document>Settings>Fonts  [x] use non-TeX fonts
 * Document>Settings>Language language-package [auto]  (or polyglossia)
 * Document>Settings>Language English
 
Günter

Re: is it possible to create a lyx file as flat ASCII file?

[Guenter Milde]

On 2014-05-10, Thirsty Camel wrote:
>
> Hmm, I spent quite a lot of time doing that without much success even with
> very simple files. Is there anyone who has working tried and made it work?
>
> Is it necessary to copy the complete header of lyx files - is there a
> minimum header and footer?

I don't know the absolute minimum, but I woudl use LyX to create a
template (empty document or some dummy content or to-be-customized
content) and then use this as a base for the script-generated LyX-file.

Günter

Re: blindtext, unicode-math, and babel won't play nice because of setmathfont

[Guenter Milde]

On 2014-05-05, asllearner wrote:

 I am trying to use a font for my main font, and also for math latin and  
 greek characters, while keeping the rest as is.
 At the same time, I want to use blindtext.
 blindtext only allows \blindmathtrue if the language has been set to  
 english:  
 http://texblog.org/2011/02/26/generating-dummy-textblindtext-with-latex-for-testing/

 This I believe I have to do via the language package custom area in the  
 document preferences, however using
 \usepackage[english]{babel}
 breaks unicode-math.

Is the use of babel mandated by blindtext?
Normally, you would use polyglossia with XeTeX/LuaTeX and Unicode fonts.

Günter

Re: How to tell LyX to add empty line after paragraphs of my style?

[Guenter Milde]

On 2014-04-28, Richard Heck wrote:
 On 04/27/2014 04:05 PM, Roman Inflianskas wrote:

 It works well except one thing: paragraphs after lists (itemize) are 
 not indented (layout uses indention instead of skip between 
 paragraphs). 

...

 The problem is that there is no empty line after list, so LaTeX 
 doesn't indent phrase Text continues I've tried different 
 options: NextNoIndent, ParbreakIsNewline, RightDelim. NextNoIndent 0 
 gives me correctly indented text in the LyX but not in the generated 
 PDF (or tex).

 The way LyX is doing this is correct. 

I don't think so:

* There are two use cases: 

  a) list embedded in a paragraph,
  b) list as a separate paragraph.
  
* In LaTeX, these are input as

First use case 
\begin{enumerate}
  \item list embedded in a paragraph, 
\end{enumerate}
Continue

Second use case:
   
\begin{enumerate}
\item list as a separate paragraph.
\end{enumerate}

Continue.


  i.e. with/without empty lines separating the list from the rest.

* In LyX, embedding would usually be done via nesting, however:

  * you cannot nest something into a paragraph,
  
  * despite the list beeing input as separate paragraph, LyX exports it to
LaTeX as embedded into the enclosing text:
  
 An environment, in principle, is part of the paragraph in which it
 appears, unless you explicitly say otherwise. 

This specific LyX behaviour is at least questionable.

The clean/consistent way would be only to embedd nested environments.

(BTW: Mathematical equations (displaymath) are 

 * a separate paragraph if surrounded by whitespace
 * embedded if glued to the surrounding text without whitespace.
 
 The problem ist, that as whitespce is not visible in the LyX window, you
 get a surprise result...)

 And, typographically, you should not want to indent the 
 following material by default. You should do so only if it begins a new 
 paragraph, i.e., a new set of ideas.

Yes, but in LyX, when I press the Return button, I do so to start a new
paragraph. When in spite of this I want to embedd something, I nest it.

 Word(TM) has done this wrong for so long that it has confused people.

LyX has had a bug with space-separated pragraphs for so long (simply
increasing parskip so that the space around lists was too large) that this
also confused both users and developers.

The typography is finally up to the document class (I would not indent
a new paragraph after a list). However we need a way to distinguish embedded
lists from lists as separate paragraphs.

Currently, LyX embeds by default and provides a hack for separating:

 If you DO want to indent the next paragraph, then put a --Separator-- 
 enviroment after your list.

Alternatively, you can use ERT (which is, of course, also a hack).

While I don't think this is correct, it may be the most pragmatic way to
keep the behaviour.

Günter

Re: problem displaying angstrom symbol

[Guenter Milde]

On 2014-05-06, Jens Nöckel wrote:

 On May 6, 2014, at 8:45 AM, Ider Ronneberger wrote:

 Hi,

 I have a problem in lyx displaying the angstom symbol using \AA within
 the math mode, i.e. if I want to view the document as pdf the angstrom
 sign is not there. However it works if I write \AA in Tex mode or
 insert it from InsertSpecial Charecters Symbols...

 On the bottom pane of the lyx display, there is a short info message.
 In one case it says Type: simple Macro:AA and in the other case (
 which works) it just says Type: simple. What is the difference? How
 can resolve this issue?

 The problem is that \AA is a text mode command, not meant for equation
 environments. In LyX, I get the correct output if I enter the Å symbol
 from the keyboard (shift-option-A on the Mac). In an equation, LyX then
 replaces that symbol by \mathring{A}, which displays properly in the
 PDF output. So you could alternatively also enter \mathring{A} in the
 LyX math editor.

Depending on what it should stand for, the correct approach is to nest it in
a text box or use \mathring{A} instead of \AA:

  \mathring{A} is usually printed in italics, it stands for a variable
  (just like x and y).
  
  \mathrm{\AA} or \text{AA} are usually printed upright (roman) and stand
  for a constant or the length unit Ångström (10 nm).
  
  All SI units (and also most non-SI units) should be written upright.
  This is also often done wrong for the micro prefix µ.
  
Günter  
  

Re: Cannot use some greek letters

[Guenter Milde]

On 2014-05-06, Steve Burnham wrote:

 [-- Type: text/plain, Encoding: quoted-printable --]

 Forum,

 I am currently writing my thesis in LyX and am writing a number of
 equations, many of which use greek letters.  All has been working fine
 until today when I needed to use the greek letter “phi”.  When trying
 to use that letter I get “could not find LaTeX command for character
 “phi” (code point 0x3d5).  I am using the latest LyX on OSX with
 MacTeX.  In the description of the error it says Some characters of
 your document are probably not representable in the chosen encoding.
  Changing the document encoding to utf8 could help.”  I tried changing
 my encoding to utf8 but it just breaks the document even more and
 doesn’t like the other greek letters.  Any advice on how to get around
 this?

Please tell, how you input the letters, which engine you use and (if
Xe/LuaTeX) if you use unicode-math.

Remember, that there are two small phi symbols in Unicode: while in Greek
text, these are just variant glyphs of the same character, in Maths they are
treated as separate symbols.

The safe way should be to input the symbols via their TeX math-macro:

  \phi and \varphi
  
(works only in a math inset). It is good style, to put all variables in a
math inset, even if used inside a sentence like:

 The variables $r$ and $\varphi$ describe the position of $\vec{c}$ in polar
 coordinates.

(This is how it should look in the LaTeX preview and source file.)

Günter 

Re: math formulae in section titles

[Guenter Milde]

On 2014-05-05, Bieniasz wrote:


 Hello,

 I am using the svmono class to write a book. My question is:

 is there any way to put mathematical formulae in the titles
 of the sections or chapters in such a way so that they have the proper
 size (adapter to the size of letters used for the titles) ?

 A simple placing of the formulae does not look nice.

This doable but not easy. I recommend to create a *minimal* example (only
required packages, just one section, ...), exporting to LaTeX, further
trimming down everything specific to LyX and then ask a TeX list like
comp.text.tex or at stackexchange.

Günter

Re: The persistent problem with svmono class and \boldsymbol font

[Guenter Milde]

On 2014-05-08, Bieniasz wrote:
 Richard Heck rgheck at lyx.org writes:

 Do you know if the problem arises simply using LaTeX?

 I have wasted a whole day trying to figure out the origin
 of the problem, and here are my conclusions:

 I think now that this is not a problem with svmono, but a general
 problem with LaTeX fonts. The svmono class assumes as default the
 Serif / Times Roman fonts. The \boldsymbol command does not work
 for this font. 

Yes, no bold math is a known (and documented) limitation of the standard 
LaTeX package for Times fonts.

 Although the bold+italic combination is properly visible
 under Lyx in the math equations, it does not appear in pdf files,
 supposedly because there are no suitable fonts. 
 All other fonts do not exhibit this deficiency, and \boldsymbol
 works OK for them.

There are other font packages with the same limitation.

 I have a feeling that this problem should be widely known,
 so that I am surprised that noone has been able to respond
 constructively to my messages. 

This may be due to the type of question. I never used the svmono class and
have no idea what it is or which packages it (in turn) requires.
Also, as this is a LaTeX limitation, the LyX list is less likely to bring an
adequate answer. I know that this is not you fault, but maybe it can explain
you the nonresponsiveness.


 Or, maybe there are better solutions?

There are better solutions: there are a number of alternative font
packages for Times-compatible maths. 

I recommend http://www.ctan.org/pkg/newtx (although I don't like its
integral sign).

A (German) survey can be found at
http://milde.users.sourceforge.net/Matheschriften/matheschriften.html


In LyX these packages could be specified in the user preamble. I don't know
if there may be problems in use combined with svmono, if yes, please post a
minimal example.

 Someone suggested to use the isomath package, but this gives
 a worse result, in my opinion, than the above solution, as for the
 Serif / Times Roman fonts the bold form does not appear in pdf.

Whiel isomath cannot solve the font problem if there is no font, I still
recommend it for reasons obvious to any reader of the documentation ;-)

Günter

Re: blindtext, unicode-math, and babel won't play nice because of setmathfont

[Guenter Milde]

On 2014-05-05, asllearner wrote:

 I am trying to use a font for my main font, and also for math latin and  
 greek characters, while keeping the rest as is.
 At the same time, I want to use blindtext.
 blindtext only allows \blindmathtrue if the language has been set to  
 english:  
 http://texblog.org/2011/02/26/generating-dummy-textblindtext-with-latex-for-testing/

 This I believe I have to do via the language package custom area in the  
 document preferences, however using
 \usepackage[english]{babel}
 breaks unicode-math.

Is the use of babel mandated by blindtext?
Normally, you would use polyglossia with XeTeX/LuaTeX and Unicode fonts.

Günter

Re: How to tell LyX to add empty line after paragraphs of my style?

[Guenter Milde]

On 2014-04-28, Richard Heck wrote:
 On 04/27/2014 04:05 PM, Roman Inflianskas wrote:

 It works well except one thing: paragraphs after lists (itemize) are 
 not indented (layout uses indention instead of skip between 
 paragraphs). 

...

 The problem is that there is no empty line after list, so LaTeX 
 doesn't indent phrase Text continues I've tried different 
 options: NextNoIndent, ParbreakIsNewline, RightDelim. NextNoIndent 0 
 gives me correctly indented text in the LyX but not in the generated 
 PDF (or tex).

 The way LyX is doing this is correct. 

I don't think so:

* There are two use cases: 

  a) list embedded in a paragraph,
  b) list as a separate paragraph.
  
* In LaTeX, these are input as

First use case 
\begin{enumerate}
  \item list embedded in a paragraph, 
\end{enumerate}
Continue

Second use case:
   
\begin{enumerate}
\item list as a separate paragraph.
\end{enumerate}

Continue.


  i.e. with/without empty lines separating the list from the rest.

* In LyX, embedding would usually be done via nesting, however:

  * you cannot nest something into a paragraph,
  
  * despite the list beeing input as separate paragraph, LyX exports it to
LaTeX as embedded into the enclosing text:
  
 An environment, in principle, is part of the paragraph in which it
 appears, unless you explicitly say otherwise. 

This specific LyX behaviour is at least questionable.

The clean/consistent way would be only to embedd nested environments.

(BTW: Mathematical equations (displaymath) are 

 * a separate paragraph if surrounded by whitespace
 * embedded if glued to the surrounding text without whitespace.
 
 The problem ist, that as whitespce is not visible in the LyX window, you
 get a surprise result...)

 And, typographically, you should not want to indent the 
 following material by default. You should do so only if it begins a new 
 paragraph, i.e., a new set of ideas.

Yes, but in LyX, when I press the Return button, I do so to start a new
paragraph. When in spite of this I want to embedd something, I nest it.

 Word(TM) has done this wrong for so long that it has confused people.

LyX has had a bug with space-separated pragraphs for so long (simply
increasing parskip so that the space around lists was too large) that this
also confused both users and developers.

The typography is finally up to the document class (I would not indent
a new paragraph after a list). However we need a way to distinguish embedded
lists from lists as separate paragraphs.

Currently, LyX embeds by default and provides a hack for separating:

 If you DO want to indent the next paragraph, then put a --Separator-- 
 enviroment after your list.

Alternatively, you can use ERT (which is, of course, also a hack).

While I don't think this is correct, it may be the most pragmatic way to
keep the behaviour.

Günter

Re: problem displaying angstrom symbol

[Guenter Milde]

On 2014-05-06, Jens Nöckel wrote:

 On May 6, 2014, at 8:45 AM, Ider Ronneberger wrote:

 Hi,

 I have a problem in lyx displaying the angstom symbol using \AA within
 the math mode, i.e. if I want to view the document as pdf the angstrom
 sign is not there. However it works if I write \AA in Tex mode or
 insert it from InsertSpecial Charecters Symbols...

 On the bottom pane of the lyx display, there is a short info message.
 In one case it says Type: simple Macro:AA and in the other case (
 which works) it just says Type: simple. What is the difference? How
 can resolve this issue?

 The problem is that \AA is a text mode command, not meant for equation
 environments. In LyX, I get the correct output if I enter the Å symbol
 from the keyboard (shift-option-A on the Mac). In an equation, LyX then
 replaces that symbol by \mathring{A}, which displays properly in the
 PDF output. So you could alternatively also enter \mathring{A} in the
 LyX math editor.

Depending on what it should stand for, the correct approach is to nest it in
a text box or use \mathring{A} instead of \AA:

  \mathring{A} is usually printed in italics, it stands for a variable
  (just like x and y).
  
  \mathrm{\AA} or \text{AA} are usually printed upright (roman) and stand
  for a constant or the length unit Ångström (10 nm).
  
  All SI units (and also most non-SI units) should be written upright.
  This is also often done wrong for the micro prefix µ.
  
Günter  
  

Re: Cannot use some greek letters

[Guenter Milde]

On 2014-05-06, Steve Burnham wrote:

 [-- Type: text/plain, Encoding: quoted-printable --]

 Forum,

 I am currently writing my thesis in LyX and am writing a number of
 equations, many of which use greek letters.  All has been working fine
 until today when I needed to use the greek letter “phi”.  When trying
 to use that letter I get “could not find LaTeX command for character
 “phi” (code point 0x3d5).  I am using the latest LyX on OSX with
 MacTeX.  In the description of the error it says Some characters of
 your document are probably not representable in the chosen encoding.
  Changing the document encoding to utf8 could help.”  I tried changing
 my encoding to utf8 but it just breaks the document even more and
 doesn’t like the other greek letters.  Any advice on how to get around
 this?

Please tell, how you input the letters, which engine you use and (if
Xe/LuaTeX) if you use unicode-math.

Remember, that there are two small phi symbols in Unicode: while in Greek
text, these are just variant glyphs of the same character, in Maths they are
treated as separate symbols.

The safe way should be to input the symbols via their TeX math-macro:

  \phi and \varphi
  
(works only in a math inset). It is good style, to put all variables in a
math inset, even if used inside a sentence like:

 The variables $r$ and $\varphi$ describe the position of $\vec{c}$ in polar
 coordinates.

(This is how it should look in the LaTeX preview and source file.)

Günter 

Re: math formulae in section titles

[Guenter Milde]

On 2014-05-05, Bieniasz wrote:


 Hello,

 I am using the svmono class to write a book. My question is:

 is there any way to put mathematical formulae in the titles
 of the sections or chapters in such a way so that they have the proper
 size (adapter to the size of letters used for the titles) ?

 A simple placing of the formulae does not look nice.

This doable but not easy. I recommend to create a *minimal* example (only
required packages, just one section, ...), exporting to LaTeX, further
trimming down everything specific to LyX and then ask a TeX list like
comp.text.tex or at stackexchange.

Günter

Re: The persistent problem with svmono class and \boldsymbol font

[Guenter Milde]

On 2014-05-08, Bieniasz wrote:
 Richard Heck rgheck at lyx.org writes:

 Do you know if the problem arises simply using LaTeX?

 I have wasted a whole day trying to figure out the origin
 of the problem, and here are my conclusions:

 I think now that this is not a problem with svmono, but a general
 problem with LaTeX fonts. The svmono class assumes as default the
 Serif / Times Roman fonts. The \boldsymbol command does not work
 for this font. 

Yes, no bold math is a known (and documented) limitation of the standard 
LaTeX package for Times fonts.

 Although the bold+italic combination is properly visible
 under Lyx in the math equations, it does not appear in pdf files,
 supposedly because there are no suitable fonts. 
 All other fonts do not exhibit this deficiency, and \boldsymbol
 works OK for them.

There are other font packages with the same limitation.

 I have a feeling that this problem should be widely known,
 so that I am surprised that noone has been able to respond
 constructively to my messages. 

This may be due to the type of question. I never used the svmono class and
have no idea what it is or which packages it (in turn) requires.
Also, as this is a LaTeX limitation, the LyX list is less likely to bring an
adequate answer. I know that this is not you fault, but maybe it can explain
you the nonresponsiveness.


 Or, maybe there are better solutions?

There are better solutions: there are a number of alternative font
packages for Times-compatible maths. 

I recommend http://www.ctan.org/pkg/newtx (although I don't like its
integral sign).

A (German) survey can be found at
http://milde.users.sourceforge.net/Matheschriften/matheschriften.html


In LyX these packages could be specified in the user preamble. I don't know
if there may be problems in use combined with svmono, if yes, please post a
minimal example.

 Someone suggested to use the isomath package, but this gives
 a worse result, in my opinion, than the above solution, as for the
 Serif / Times Roman fonts the bold form does not appear in pdf.

Whiel isomath cannot solve the font problem if there is no font, I still
recommend it for reasons obvious to any reader of the documentation ;-)

Günter

Re: blindtext, unicode-math, and babel won't play nice because of setmathfont

[Guenter Milde]

On 2014-05-05, asllearner wrote:

> I am trying to use a font for my main font, and also for math latin and  
> greek characters, while keeping the rest as is.
> At the same time, I want to use blindtext.
> blindtext only allows \blindmathtrue if the language has been set to  
> english:  
> http://texblog.org/2011/02/26/generating-dummy-textblindtext-with-latex-for-testing/

> This I believe I have to do via the language package custom area in the  
> document preferences, however using
> \usepackage[english]{babel}
> breaks unicode-math.

Is the use of babel mandated by "blindtext"?
Normally, you would use "polyglossia" with XeTeX/LuaTeX and Unicode fonts.

Günter

Re: How to tell LyX to add empty line after paragraphs of my style?

[Guenter Milde]

On 2014-04-28, Richard Heck wrote:
> On 04/27/2014 04:05 PM, Roman Inflianskas wrote:

>> It works well except one thing: paragraphs after lists (itemize) are 
>> not indented (layout uses indention instead of skip between 
>> paragraphs). 

...

>> The problem is that there is no empty line after list, so LaTeX 
>> doesn't indent phrase "Text continues...". I've tried different 
>> options: NextNoIndent, ParbreakIsNewline, RightDelim. "NextNoIndent 0" 
>> gives me correctly indented text in the LyX but not in the generated 
>> PDF (or tex).

> The way LyX is doing this is correct. 

I don't think so:

* There are two use cases: 

  a) list embedded in a paragraph,
  b) list as a separate paragraph.
  
* In LaTeX, these are input as

First use case 
\begin{enumerate}
  \item list embedded in a paragraph, 
\end{enumerate}
Continue

Second use case:
   
\begin{enumerate}
\item list as a separate paragraph.
\end{enumerate}

Continue.


  i.e. with/without empty lines separating the list from the rest.

* In LyX, embedding would usually be done via "nesting", however:

  * you cannot nest something into a paragraph,
  
  * despite the list beeing input as separate paragraph, LyX exports it to
LaTeX as embedded into the enclosing text:
  
> An environment, in principle, is part of the paragraph in which it
> appears, unless you explicitly say otherwise. 

This specific LyX behaviour is at least questionable.

The clean/consistent way would be only to embedd nested environments.

(BTW: Mathematical equations (displaymath) are 

 * a separate paragraph if surrounded by whitespace
 * embedded if "glued" to the surrounding text without whitespace.
 
 The problem ist, that as whitespce is not visible in the LyX window, you
 get a surprise result...)

> And, typographically, you should not want to indent the 
> following material by default. You should do so only if it begins a new 
> paragraph, i.e., a new set of ideas.

Yes, but in LyX, when I press the Return button, I do so to start a new
paragraph. When in spite of this I want to embedd something, I nest it.

> Word(TM) has done this wrong for so long that it has confused people.

LyX has had a bug with space-separated pragraphs for so long (simply
increasing parskip so that the space around lists was too large) that this
also confused both users and developers.

The typography is finally up to the document class (I would not indent
a new paragraph after a list). However we need a way to distinguish embedded
lists from lists as separate paragraphs.

Currently, LyX embeds by default and provides a hack for separating:

> If you DO want to indent the next paragraph, then put a "--Separator--" 
> enviroment after your list.

Alternatively, you can use ERT (which is, of course, also a hack).

While I don't think this is "correct", it may be the most pragmatic way to
keep the behaviour.

Günter

Re: problem displaying angstrom symbol

[Guenter Milde]

On 2014-05-06, Jens Nöckel wrote:

> On May 6, 2014, at 8:45 AM, Ider Ronneberger wrote:

>> Hi,

>> I have a problem in lyx displaying the angstom symbol using \AA within
>> the math mode, i.e. if I want to view the document as pdf the angstrom
>> sign is not there. However it works if I write \AA in Tex mode or
>> insert it from Insert>Special Charecters> Symbols...

>> On the bottom pane of the lyx display, there is a short info message.
>> In one case it says "Type: simple Macro:AA" and in the other case (
>> which works) it just says "Type: simple". What is the difference? How
>> can resolve this issue?

> The problem is that \AA is a text mode command, not meant for equation
> environments. In LyX, I get the correct output if I enter the Å symbol
> from the keyboard (shift-option-A on the Mac). In an equation, LyX then
> replaces that symbol by \mathring{A}, which displays properly in the
> PDF output. So you could alternatively also enter \mathring{A} in the
> LyX math editor.

Depending on what it should stand for, the correct approach is to nest it in
a text box or use \mathring{A} instead of \AA:

  \mathring{A} is usually printed in italics, it stands for a variable
  (just like x and y).
  
  \mathrm{\AA} or \text{AA} are usually printed upright (roman) and stand
  for a constant or the length unit Ångström (10 nm).
  
  All SI units (and also most non-SI units) should be written upright.
  This is also often done wrong for the micro prefix µ.
  
Günter  
  

Re: Cannot use some greek letters

[Guenter Milde]

On 2014-05-06, Steve Burnham wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> Forum,

> I am currently writing my thesis in LyX and am writing a number of
> equations, many of which use greek letters.  All has been working fine
> until today when I needed to use the greek letter “phi”.  When trying
> to use that letter I get “could not find LaTeX command for character
> “phi” (code point 0x3d5).  I am using the latest LyX on OSX with
> MacTeX.  In the description of the error it says "Some characters of
> your document are probably not representable in the chosen encoding.
>  Changing the document encoding to utf8 could help.”  I tried changing
> my encoding to utf8 but it just breaks the document even more and
> doesn’t like the other greek letters.  Any advice on how to get around
> this?

Please tell, how you input the letters, which engine you use and (if
Xe/LuaTeX) if you use unicode-math.

Remember, that there are two small phi symbols in Unicode: while in Greek
text, these are just variant glyphs of the same character, in Maths they are
treated as separate symbols.

The safe way should be to input the symbols via their TeX math-macro:

  \phi and \varphi
  
(works only in a math inset). It is good style, to put all variables in a
math inset, even if used inside a sentence like:

 The variables $r$ and $\varphi$ describe the position of $\vec{c}$ in polar
 coordinates.

(This is how it should look in the LaTeX preview and source file.)

Günter 

Re: math formulae in section titles

[Guenter Milde]

On 2014-05-05, Bieniasz wrote:


> Hello,

> I am using the svmono class to write a book. My question is:

> is there any way to put mathematical formulae in the titles
> of the sections or chapters in such a way so that they have the proper
> size (adapter to the size of letters used for the titles) ?

> A simple placing of the formulae does not look nice.

This doable but not easy. I recommend to create a *minimal* example (only
required packages, just one section, ...), exporting to LaTeX, further
trimming down everything specific to LyX and then ask a TeX list like
comp.text.tex or at stackexchange.

Günter

Re: The persistent problem with svmono class and \boldsymbol font

[Guenter Milde]

On 2014-05-08, Bieniasz wrote:
> Richard Heck  lyx.org> writes:

>> Do you know if the problem arises simply using LaTeX?

> I have wasted a whole day trying to figure out the origin
> of the problem, and here are my conclusions:

> I think now that this is not a problem with svmono, but a general
> problem with LaTeX fonts. The svmono class assumes as default the
> Serif / Times Roman fonts. The \boldsymbol command does not work
> for this font. 

Yes, no bold math is a known (and documented) limitation of the standard 
LaTeX package for Times fonts.

> Although the bold+italic combination is properly visible
> under Lyx in the math equations, it does not appear in pdf files,
> supposedly because there are no suitable fonts. 
> All other fonts do not exhibit this deficiency, and \boldsymbol
> works OK for them.

There are other font packages with the same limitation.

> I have a feeling that this problem should be widely known,
> so that I am surprised that noone has been able to respond
> constructively to my messages. 

This may be due to the type of question. I never used the svmono class and
have no idea what it is or which packages it (in turn) requires.
Also, as this is a LaTeX limitation, the LyX list is less likely to bring an
adequate answer. I know that this is not you fault, but maybe it can explain
you the nonresponsiveness.


> Or, maybe there are better solutions?

There are better solutions: there are a number of alternative font
packages for Times-compatible maths. 

I recommend http://www.ctan.org/pkg/newtx (although I don't like its
integral sign).

A (German) survey can be found at
http://milde.users.sourceforge.net/Matheschriften/matheschriften.html


In LyX these packages could be specified in the user preamble. I don't know
if there may be problems in use combined with svmono, if yes, please post a
minimal example.

> Someone suggested to use the isomath package, but this gives
> a worse result, in my opinion, than the above solution, as for the
> Serif / Times Roman fonts the bold form does not appear in pdf.

Whiel isomath cannot solve the font problem if there is no font, I still
recommend it for reasons obvious to any reader of the documentation ;-)

Günter

Re: Ctrl-Enter handling is different whether AMS math is used explicitly or automatically

[Guenter Milde]

On 2014-05-02, Jean-Marc Lasgouttes wrote:
 01/05/2014 23:59, Wil:
 Since I never needed to explicitly enable amsmath until I started
 working with parent/child documents, I never noticed this behavior until
 now.

 The behavior makes sense to me after I thought about it for a minute,
 but it was surprising nonetheless.  I've seen this behavior in versions
 2.0.3, 2.0.6, and 2.1.0 in (debian) Linux; and 2.0.3 and 2.1.0 in Mac OS
 X (where the keystroke is Command-Enter.)

 I agree that it is strange. Would you have an idea on how to improve the 
 behavior? I warn you though that add a new prefrence is not a valid 
 answer :)

Maybe 

Use AMS-math:
( ) no
( ) automatically (only if absolutely required)
( ) automatically (preferred alternative)
( ) always

Günter

Re: Ctrl-Enter handling is different whether AMS math is used explicitly or automatically

[Guenter Milde]

On 2014-05-02, Jean-Marc Lasgouttes wrote:
 01/05/2014 23:59, Wil:
 Since I never needed to explicitly enable amsmath until I started
 working with parent/child documents, I never noticed this behavior until
 now.

 The behavior makes sense to me after I thought about it for a minute,
 but it was surprising nonetheless.  I've seen this behavior in versions
 2.0.3, 2.0.6, and 2.1.0 in (debian) Linux; and 2.0.3 and 2.1.0 in Mac OS
 X (where the keystroke is Command-Enter.)

 I agree that it is strange. Would you have an idea on how to improve the 
 behavior? I warn you though that add a new prefrence is not a valid 
 answer :)

Maybe 

Use AMS-math:
( ) no
( ) automatically (only if absolutely required)
( ) automatically (preferred alternative)
( ) always

Günter

Re: Ctrl-Enter handling is different whether AMS math is used explicitly or automatically

[Guenter Milde]

On 2014-05-02, Jean-Marc Lasgouttes wrote:
> 01/05/2014 23:59, Wil:
>> Since I never needed to explicitly enable amsmath until I started
>> working with parent/child documents, I never noticed this behavior until
>> now.

>> The behavior makes sense to me after I thought about it for a minute,
>> but it was surprising nonetheless.  I've seen this behavior in versions
>> 2.0.3, 2.0.6, and 2.1.0 in (debian) Linux; and 2.0.3 and 2.1.0 in Mac OS
>> X (where the keystroke is Command-Enter.)

> I agree that it is strange. Would you have an idea on how to improve the 
> behavior? I warn you though that "add a new prefrence" is not a valid 
> answer :)

Maybe 

Use AMS-math:
( ) no
( ) automatically (only if absolutely required)
( ) automatically (preferred alternative)
( ) always

Günter

Re: umlaute in Lilypond Lyx file

[Guenter Milde]

On 2014-04-16, Wolfgang Engelmann wrote:
 Am 16.04.2014 16:32, schrieb stefano franchi:


   ! Package fontenc Error: Encoding file `eu2enc.def' not found.

...

 ! LaTeX Error: File `xunicode.sty' not found.

...

 It seems to me you are not use the utf8 encoding (which you should, with
 Xetex). Try compiling the file I sent you and let me know what happens.

With use non-TeX fonts, the LaTeX encoding is always utf-8.
It rather seems like the xunicode package and the EU1 and EU2 font encodings
are not installed.

On my Debian system,

  apt-file find eu2enc.def

revealed

  texlive-xetex: /usr/share/texlive/texmf-dist/tex/latex/euenc/eu2enc.def

Please check, if the texlive-xetex package is installed and if you find
eu2enc.def under thiis path. Also, ckeck 

  kpsewhich eu2enc.def
  
and the same for xunicode.sty.  


 I tried the file you sent and it shows the same error I had reported.
 Were is utf8 encoding set in LyX? Could not find it in the diverse help
 files; in the User's Guide it says, Lyx is always UTF8 encoded.

While the LyX file is utf8-encoded (since quite some time), the encoding of
the generated LaTeX file is configurable.

With use non-TeX fonts true, it is utf8, with TeX fonts, it can be set under
 
 DocumentSettingsLanguageEncodingOther...
 
from the alphabetically sorted drop-down list select Unicode (utf8)
(the most sensible default for any document using Latin, Greek or Cyrillic
script, btw.).

With this setting, you should also be able to use TeX fonts with lilypond.

Günter

Re: umlaute in Lilypond Lyx file

[Guenter Milde]

On 2014-04-16, Wolfgang Engelmann wrote:
 Am 16.04.2014 16:32, schrieb stefano franchi:


   ! Package fontenc Error: Encoding file `eu2enc.def' not found.

...

 ! LaTeX Error: File `xunicode.sty' not found.

...

 It seems to me you are not use the utf8 encoding (which you should, with
 Xetex). Try compiling the file I sent you and let me know what happens.

With use non-TeX fonts, the LaTeX encoding is always utf-8.
It rather seems like the xunicode package and the EU1 and EU2 font encodings
are not installed.

On my Debian system,

  apt-file find eu2enc.def

revealed

  texlive-xetex: /usr/share/texlive/texmf-dist/tex/latex/euenc/eu2enc.def

Please check, if the texlive-xetex package is installed and if you find
eu2enc.def under thiis path. Also, ckeck 

  kpsewhich eu2enc.def
  
and the same for xunicode.sty.  


 I tried the file you sent and it shows the same error I had reported.
 Were is utf8 encoding set in LyX? Could not find it in the diverse help
 files; in the User's Guide it says, Lyx is always UTF8 encoded.

While the LyX file is utf8-encoded (since quite some time), the encoding of
the generated LaTeX file is configurable.

With use non-TeX fonts true, it is utf8, with TeX fonts, it can be set under
 
 DocumentSettingsLanguageEncodingOther...
 
from the alphabetically sorted drop-down list select Unicode (utf8)
(the most sensible default for any document using Latin, Greek or Cyrillic
script, btw.).

With this setting, you should also be able to use TeX fonts with lilypond.

Günter

Re: umlaute in Lilypond Lyx file

[Guenter Milde]

On 2014-04-16, Wolfgang Engelmann wrote:
> Am 16.04.2014 16:32, schrieb stefano franchi:


>>>   ! Package fontenc Error: Encoding file `eu2enc.def' not found.

...

>>> ! LaTeX Error: File `xunicode.sty' not found.

...

>> It seems to me you are not use the utf8 encoding (which you should, with
>> Xetex). Try compiling the file I sent you and let me know what happens.

With "use non-TeX fonts", the "LaTeX encoding" is always utf-8.
It rather seems like the xunicode package and the EU1 and EU2 font encodings
are not installed.

On my Debian system,

  apt-file find eu2enc.def

revealed

  texlive-xetex: /usr/share/texlive/texmf-dist/tex/latex/euenc/eu2enc.def

Please check, if the texlive-xetex package is installed and if you find
eu2enc.def under thiis path. Also, ckeck 

  kpsewhich eu2enc.def
  
and the same for xunicode.sty.  


> I tried the file you sent and it shows the same error I had reported.
> Were is utf8 encoding set in LyX? Could not find it in the diverse help
> files; in the User's Guide it says, Lyx is always UTF8 encoded.

While the LyX file is utf8-encoded (since quite some time), the encoding of
the generated LaTeX file is configurable.

With "use non-TeX fonts" true, it is utf8, with TeX fonts, it can be set under
 
 Document>Settings>Language>Encoding>Other>...
 
from the alphabetically sorted drop-down list select Unicode (utf8)
(the most sensible default for any document using Latin, Greek or Cyrillic
script, btw.).

With this setting, you should also be able to use TeX fonts with lilypond.

Günter

Re: umlaute in Lilypond Lyx file

[Guenter Milde]

 I use pdflatex. So I have to install Libertine and use XeLaTex? Never 
 used it. Is it tricky to use?

 Guenter Milde, 2011:
 Alternatively,
 In LyX 2.0, you can use 'non-TeX fonts' and choose Linux Libertine 
 Biolinum if these are installed on your system. Then you will compile
 your documents with XeTeX.

Here, I was telling about the non-TeX fonts fonts switch with Libertine
beeing just one example font with a wide coverage of glyphs.

Remember, that this is just one way of using Libertine. There is also
support for Libertine with 8-bit TeX engines via a set of TeX-encoded
Libertine font files.


Unfortunately, I don't know enaugh about the TeX-Lilypond interaction, so I
cannot tell whether switching to XeTeX or LuaTeX will help.
However, if LICR macros like 
  
  Gr\u\s e
  
do not help, it may be Lilypond uses utf-8 encoding internally and you are
passing text to it and this should be utf-8 encoded, too.

In this case, you could, of course, also try pdflatex with the Unicode
(utf-8) input-encoding (in LyX called LaTeX encoding).

Günter

Re: umlaute in Lilypond Lyx file

[Guenter Milde]

 I use pdflatex. So I have to install Libertine and use XeLaTex? Never 
 used it. Is it tricky to use?

 Guenter Milde, 2011:
 Alternatively,
 In LyX 2.0, you can use 'non-TeX fonts' and choose Linux Libertine 
 Biolinum if these are installed on your system. Then you will compile
 your documents with XeTeX.

Here, I was telling about the non-TeX fonts fonts switch with Libertine
beeing just one example font with a wide coverage of glyphs.

Remember, that this is just one way of using Libertine. There is also
support for Libertine with 8-bit TeX engines via a set of TeX-encoded
Libertine font files.


Unfortunately, I don't know enaugh about the TeX-Lilypond interaction, so I
cannot tell whether switching to XeTeX or LuaTeX will help.
However, if LICR macros like 
  
  Gr\u\s e
  
do not help, it may be Lilypond uses utf-8 encoding internally and you are
passing text to it and this should be utf-8 encoded, too.

In this case, you could, of course, also try pdflatex with the Unicode
(utf-8) input-encoding (in LyX called LaTeX encoding).

Günter

Re: umlaute in Lilypond Lyx file

[Guenter Milde]

> I use pdflatex. So I have to install Libertine and use XeLaTex? Never 
> used it. Is it tricky to use?

> Guenter Milde, 2011:
> Alternatively,
>> In LyX 2.0, you can use 'non-TeX fonts' and choose Linux Libertine &
>> Biolinum if these are installed on your system. Then you will compile
>> your documents with XeTeX.

Here, I was telling about the "non-TeX fonts" fonts switch with Libertine
beeing just one example font with a wide coverage of glyphs.

Remember, that this is just one way of using Libertine. There is also
support for Libertine with 8-bit TeX engines via a set of TeX-encoded
Libertine font files.


Unfortunately, I don't know enaugh about the TeX-Lilypond interaction, so I
cannot tell whether switching to XeTeX or LuaTeX will help.
However, if LICR macros like 
  
  Gr\"u\s e
  
do not help, it may be Lilypond uses utf-8 encoding internally and you are
passing text to it and this should be utf-8 encoded, too.

In this case, you could, of course, also try pdflatex with the "Unicode
(utf-8)" input-encoding (in LyX called LaTeX encoding).

Günter

Re: A small bug maybe and a small request

[Guenter Milde]

On 2014-04-07, Murat Yildizoglu wrote:

 I use Lyx under OSX Mavericks.
 I have discovered a small problem in beta2 yesterday: \Omega is invisible
 in a math inset (but becomes visible when the cursor leaves it).
 I have consequently installed the RC1 to check if this problem has been
 solved. It seems that it is replaced by a smaller one: \Omega is replaced
 by W in the math inset (but appears as \Omega out of it. \VarOmega has also
 a problem by the way.

I suppose, this is a problem of the installed screen-font.
I also suppose, you use the instant-preview, that replaces the math inset
with a LaTeX rendering when not editing it.

Are the \Omegas the only affected letters or does this affect all the Greek
symbols?

Are you able to see Greek letters in other editors?

 I attach a small lyx file in which you could check the problem (maybe it is
 OSX only, I cannot check it).
 Can you confirm it on OSX or other OS?

 I have also observed another point that bugs me a little bit (maybe I am
 missing the rationale of this): When I am typing math and try to insert a
 superscript or an exponent to an expression using ^ Lyx uses instead an
 accented letter if this letter accepts an accent (like i, j, e, etc.). One
 than gets x\hat{\imath}  instead of x^{i} . It would be nice to neutralize
 in math insets this default behavior that is perfectly reasonable in a word
 in rm.

It seems you use a keymap with dead keys. This is usually not a
LyX-specific, but a system wide setting. 

If you like it (generally), you may just keep it and remember to press the
accents *twice* for literal insertion or passing on to the math-editor:

   press   x ^ ^ i  
   to get  x^{i}
   
If you don't like it, use a different keymap, either globally or for LyX
(unfortunately, I don't know how to select the keymap under OSX).

Günter

 Do you think at it would be a good idea to change the default behavior (if
 this is possible and easy of course)?

 Best regards,

 Murat

Re: A small bug maybe and a small request

[Guenter Milde]

On 2014-04-07, Murat Yildizoglu wrote:

 I use Lyx under OSX Mavericks.
 I have discovered a small problem in beta2 yesterday: \Omega is invisible
 in a math inset (but becomes visible when the cursor leaves it).
 I have consequently installed the RC1 to check if this problem has been
 solved. It seems that it is replaced by a smaller one: \Omega is replaced
 by W in the math inset (but appears as \Omega out of it. \VarOmega has also
 a problem by the way.

I suppose, this is a problem of the installed screen-font.
I also suppose, you use the instant-preview, that replaces the math inset
with a LaTeX rendering when not editing it.

Are the \Omegas the only affected letters or does this affect all the Greek
symbols?

Are you able to see Greek letters in other editors?

 I attach a small lyx file in which you could check the problem (maybe it is
 OSX only, I cannot check it).
 Can you confirm it on OSX or other OS?

 I have also observed another point that bugs me a little bit (maybe I am
 missing the rationale of this): When I am typing math and try to insert a
 superscript or an exponent to an expression using ^ Lyx uses instead an
 accented letter if this letter accepts an accent (like i, j, e, etc.). One
 than gets x\hat{\imath}  instead of x^{i} . It would be nice to neutralize
 in math insets this default behavior that is perfectly reasonable in a word
 in rm.

It seems you use a keymap with dead keys. This is usually not a
LyX-specific, but a system wide setting. 

If you like it (generally), you may just keep it and remember to press the
accents *twice* for literal insertion or passing on to the math-editor:

   press   x ^ ^ i  
   to get  x^{i}
   
If you don't like it, use a different keymap, either globally or for LyX
(unfortunately, I don't know how to select the keymap under OSX).

Günter

 Do you think at it would be a good idea to change the default behavior (if
 this is possible and easy of course)?

 Best regards,

 Murat

Re: A small bug maybe and a small request

[Guenter Milde]

On 2014-04-07, Murat Yildizoglu wrote:

> I use Lyx under OSX Mavericks.
> I have discovered a small problem in beta2 yesterday: \Omega is invisible
> in a math inset (but becomes visible when the cursor leaves it).
> I have consequently installed the RC1 to check if this problem has been
> solved. It seems that it is replaced by a smaller one: \Omega is replaced
> by W in the math inset (but appears as \Omega out of it. \VarOmega has also
> a problem by the way.

I suppose, this is a problem of the installed screen-font.
I also suppose, you use the "instant-preview", that replaces the math inset
with a LaTeX rendering when not editing it.

Are the \Omegas the only affected letters or does this affect all the Greek
symbols?

Are you able to see Greek letters in other editors?

> I attach a small lyx file in which you could check the problem (maybe it is
> OSX only, I cannot check it).
> Can you confirm it on OSX or other OS?

> I have also observed another point that bugs me a little bit (maybe I am
> missing the rationale of this): When I am typing math and try to insert a
> superscript or an exponent to an expression using ^ Lyx uses instead an
> accented letter if this letter accepts an accent (like i, j, e, etc.). One
> than gets x\hat{\imath}  instead of x^{i} . It would be nice to neutralize
> in math insets this default behavior that is perfectly reasonable in a word
> in rm.

It seems you use a keymap with "dead keys". This is usually not a
LyX-specific, but a system wide setting. 

If you like it (generally), you may just keep it and remember to press the
accents *twice* for literal insertion or passing on to the math-editor:

   press   x ^ ^ i  
   to get  x^{i}
   
If you don't like it, use a different keymap, either globally or for LyX
(unfortunately, I don't know how to select the keymap under OSX).

Günter

> Do you think at it would be a good idea to change the default behavior (if
> this is possible and easy of course)?

> Best regards,

> Murat

Re: ANNOUNCE: LyX version 2.1.0 (rc1)

[Guenter Milde]

On 2014-04-01, Wolfgang Keller wrote:

 Probably the only thing that's still left from the original LyTeX (must
 have been 1.6.x back then) is the folder structure and the startupt
 script.

Hey, if you have a fairly uncommon setup, dont expect everything to work out
of the box!

...

 So if anything doesn't work, I'll just sent a corresponding rant to the
 list and roll back.

If you would be more polite instead of sending a rant, I would say this
is OK.

...

 This can destroy your LyX settings so that it can become unusable.

 It won't destroy anything that I can't roll back by simply trashing
 the LyX subfolder that's kaputt and by replacing it with the last
 known working version.

 That is *one* of the *many* advantages of installer-free application
 distribution.

 No need for installers, no need for uninstallers, backups are trivial
 and so are rollbacks.

So, why do you use the installer at all?

Günter

Re: ANNOUNCE: LyX version 2.1.0 (rc1)

[Guenter Milde]

On 2014-04-01, Wolfgang Keller wrote:

 Probably the only thing that's still left from the original LyTeX (must
 have been 1.6.x back then) is the folder structure and the startupt
 script.

Hey, if you have a fairly uncommon setup, dont expect everything to work out
of the box!

...

 So if anything doesn't work, I'll just sent a corresponding rant to the
 list and roll back.

If you would be more polite instead of sending a rant, I would say this
is OK.

...

 This can destroy your LyX settings so that it can become unusable.

 It won't destroy anything that I can't roll back by simply trashing
 the LyX subfolder that's kaputt and by replacing it with the last
 known working version.

 That is *one* of the *many* advantages of installer-free application
 distribution.

 No need for installers, no need for uninstallers, backups are trivial
 and so are rollbacks.

So, why do you use the installer at all?

Günter

Re: ANNOUNCE: LyX version 2.1.0 (rc1)

[Guenter Milde]

On 2014-04-01, Wolfgang Keller wrote:

> Probably the only thing that's still left from the original LyTeX (must
> have been 1.6.x back then) is the folder structure and the startupt
> script.

Hey, if you have a fairly uncommon setup, dont expect everything to work out
of the box!

...

> So if anything doesn't work, I'll just sent a corresponding rant to the
> list and "roll back".

If you would be more polite instead of sending a rant, I would say this
is OK.

...

>> This can destroy your LyX settings so that it can become unusable.

> It won't destroy anything that I can't roll back by simply trashing
> the LyX subfolder that's "kaputt" and by replacing it with the last
> known working version.

> That is *one* of the *many* advantages of installer-free application
> distribution.

> No need for installers, no need for uninstallers, backups are trivial
> and so are "rollbacks".

So, why do you use the installer at all?

Günter

Re: Table width

[Guenter Milde]

On 2014-03-30, Uwe Stöhr wrote:
 Am 30.03.2014 07:57, schrieb Carsten Jahn:

 I didnt mean long tables but wide ones, and word, as much as I hate to
 admit, is better in that one IMHO, as you could just drag your table till
 it fits,

 That is just the opposite of the WYSIWYM concept of LyX and LaTeX. The
 concept is to let the software decide after professional rules what
 means it fits.

However, automatic table width is a real shortcoming of LaTeX.
Things work fine, as long as all cell entries are short one-liners.
However,

* there is no professional rule for line wrapping in a column unless it
  has a fixed width.
  
* without looking at the output, you cannot know, whether a table fits on
  the page or is too wide!!!
  
* there is no support for manual line-breaks in a column without
  fixed width (unless you use \shortstack in an ERT).
  
* setting a fixed width requires opening a dialogue and inserting values
  (if you want a fixed width for the whole table, this requires complicated
  mathematical calculations as well - in this case the trial and error
  method may even be faster than looking up the documentation on column
  separating space etc...).
  
All this is a clear distraction from concentrating on content and WWAATS
(what we are able to show) is still far from what I mean.


 while you have to manually input the parameters in LyX and compile
 it for every trial and error.

 Note that this is not the way you should go. If you try to fit
 everything as you like it all the time you look a lot of time and when
 you modify your document you will have to do this again and again. So
 better concentrate on writing and do the fine-tuning when the document
 is really ready.

However, this still means I cannot see the whole table unless fine
tuning and I have to fine tune (fixing tables maybe 5 times as wide as
the page) by calculating column widths and inserting the result for every
table at the end of the process.

If it were not for the advantages in other parts of the process, I would
select/recomment an alternative system.

Let's be honest about both, strenghts and weaknesses.

Günter

Re: Table width

[Guenter Milde]

On 2014-03-30, Uwe Stöhr wrote:
 Am 30.03.2014 07:57, schrieb Carsten Jahn:

 I didnt mean long tables but wide ones, and word, as much as I hate to
 admit, is better in that one IMHO, as you could just drag your table till
 it fits,

 That is just the opposite of the WYSIWYM concept of LyX and LaTeX. The
 concept is to let the software decide after professional rules what
 means it fits.

However, automatic table width is a real shortcoming of LaTeX.
Things work fine, as long as all cell entries are short one-liners.
However,

* there is no professional rule for line wrapping in a column unless it
  has a fixed width.
  
* without looking at the output, you cannot know, whether a table fits on
  the page or is too wide!!!
  
* there is no support for manual line-breaks in a column without
  fixed width (unless you use \shortstack in an ERT).
  
* setting a fixed width requires opening a dialogue and inserting values
  (if you want a fixed width for the whole table, this requires complicated
  mathematical calculations as well - in this case the trial and error
  method may even be faster than looking up the documentation on column
  separating space etc...).
  
All this is a clear distraction from concentrating on content and WWAATS
(what we are able to show) is still far from what I mean.


 while you have to manually input the parameters in LyX and compile
 it for every trial and error.

 Note that this is not the way you should go. If you try to fit
 everything as you like it all the time you look a lot of time and when
 you modify your document you will have to do this again and again. So
 better concentrate on writing and do the fine-tuning when the document
 is really ready.

However, this still means I cannot see the whole table unless fine
tuning and I have to fine tune (fixing tables maybe 5 times as wide as
the page) by calculating column widths and inserting the result for every
table at the end of the process.

If it were not for the advantages in other parts of the process, I would
select/recomment an alternative system.

Let's be honest about both, strenghts and weaknesses.

Günter

Re: Table width

[Guenter Milde]

On 2014-03-30, Uwe Stöhr wrote:
> Am 30.03.2014 07:57, schrieb Carsten Jahn:

>> I didnt mean long tables but wide ones, and word, as much as I hate to
>> admit, is better in that one IMHO, as you could just drag your table till
>> it fits,

> That is just the opposite of the WYSIWYM concept of LyX and LaTeX. The
> concept is to let the software decide after professional rules what
> means "it fits".

However, automatic table width is a real shortcoming of LaTeX.
Things work fine, as long as all cell entries are short one-liners.
However,

* there is no "professional rule" for line wrapping in a column unless it
  has a fixed width.
  
* without looking at the output, you cannot know, whether a table fits on
  the page or is too wide!!!
  
* there is no support for manual line-breaks in a column without
  fixed width (unless you use \shortstack in an ERT).
  
* setting a fixed width requires opening a dialogue and inserting values
  (if you want a fixed width for the whole table, this requires complicated
  mathematical calculations as well - in this case the trial and error
  method may even be faster than looking up the documentation on column
  separating space etc...).
  
All this is a clear distraction from concentrating on content and WWAATS
(what we are able to show) is still far from what I mean.


>> while you have to manually input the parameters in LyX and compile
>> it for every trial and error.

> Note that this is not the way you should go. If you try to fit
> everything as you like it all the time you look a lot of time and when
> you modify your document you will have to do this again and again. So
> better concentrate on writing and do the fine-tuning when the document
> is really ready.

However, this still means I cannot see the whole table unless "fine
tuning" and I have to fine tune (fixing tables maybe 5 times as wide as
the page) by calculating column widths and inserting the result for every
table at the end of the process.

If it were not for the advantages in other parts of the process, I would
select/recomment an alternative system.

Let's be honest about both, strenghts and weaknesses.

Günter

Re: Struggling again on lyx--doc/odt conversion

[Guenter Milde]

On 2014-02-12, stefano franchi wrote:

 And switching from LuaTeX to pdflatex is not
 really an option, as the document and the bibliography have a mix of
 English, French, and Italian, with lots of diacritics. I would have to
 manually convert everything to Latex's codes, I guess. Or find a tool that
 does it for me.

As long as you do not include esoteric Unicode characters, also 8-bit
tex engines (pdflatex/latex) should work as long as you set the right
LaTeX input encoding.

  In LyX, this means DocumentSettingsLanguageEncoding: Unicode (utf8).

  In the LaTeX source, this translates to \usepackage[utf8]{inputenc}

This should do the trick for Latin (including Latin-extended and many more
diacritics), Greek (with a not too old TeX distribution) and Cyrillic
script.

BibTeX has some problems with Unicode, but BibLaTeX should work with
8-bit tex engines, too.

As I am working on LaTeX Unicode support, I would be interested in
problem reports.

Günter

Re: Struggling again on lyx--doc/odt conversion

[Guenter Milde]

On 2014-02-12, stefano franchi wrote:

 And switching from LuaTeX to pdflatex is not
 really an option, as the document and the bibliography have a mix of
 English, French, and Italian, with lots of diacritics. I would have to
 manually convert everything to Latex's codes, I guess. Or find a tool that
 does it for me.

As long as you do not include esoteric Unicode characters, also 8-bit
tex engines (pdflatex/latex) should work as long as you set the right
LaTeX input encoding.

  In LyX, this means DocumentSettingsLanguageEncoding: Unicode (utf8).

  In the LaTeX source, this translates to \usepackage[utf8]{inputenc}

This should do the trick for Latin (including Latin-extended and many more
diacritics), Greek (with a not too old TeX distribution) and Cyrillic
script.

BibTeX has some problems with Unicode, but BibLaTeX should work with
8-bit tex engines, too.

As I am working on LaTeX Unicode support, I would be interested in
problem reports.

Günter

Re: Struggling again on lyx-->doc/odt conversion

[Guenter Milde]

On 2014-02-12, stefano franchi wrote:

> And switching from LuaTeX to pdflatex is not
> really an option, as the document and the bibliography have a mix of
> English, French, and Italian, with lots of diacritics. I would have to
> manually convert everything to Latex's codes, I guess. Or find a tool that
> does it for me.

As long as you do not include "esoteric" Unicode characters, also 8-bit
tex engines (pdflatex/latex) should work as long as you set the right
LaTeX input encoding.

  In LyX, this means Document>Settings>Language>Encoding: Unicode (utf8).

  In the LaTeX source, this translates to \usepackage[utf8]{inputenc}

This should do the trick for Latin (including Latin-extended and many more
diacritics), Greek (with a not too old TeX distribution) and Cyrillic
script.

BibTeX has some problems with Unicode, but BibLaTeX should work with
8-bit tex engines, too.

As I am working on LaTeX Unicode support, I would be interested in
problem reports.

Günter

Re: thinspace too wide

[Guenter Milde]

On 2014-02-04, Jürgen Spitzmüller wrote:

 [-- Type: text/plain, Encoding: quoted-printable --]

 2014-02-04 Marcelo Acuña marceloacu...@yahoo.com:

 hello
  I want to get control over wide of thinspace.
  The present is too wide.


 The original definition is
 \def\thinspace{\kern .16667em }

 go change it in the preamble.


  Plus I want that thinspace make a hard link between parts and not be
 broken by hypenation.

 This I don't understand.

I suppose the OP is looking for a non-breaking thin space

202FNARROW NO-BREAK SPACE
* commonly abbreviated NNBSP
* a narrow form of a no-break space, typically the width of a thin 
space or a mid space
x (no-break space - 00A0)
x (four-per-em space - 2005)
x (thin space - 2009)
# noBreak 0020


LyX's unicodesymbols Unicode-LaTeX conversion file says:

0x202f \\,\\,  # NARROW NO-BREAK SPACE

So, Marcelo, you can either input the unicode character 
or (as ERT/raw latex) the command \, 
or redefine \thinspace in the preamble to be \,

Günter

Re: thinspace too wide

[Guenter Milde]

On 2014-02-05, Marcelo Acuña wrote:

 [-- Type: text/plain, Encoding: quoted-printable --]

 OK Guenter, and, How I can redefine de narrow non-brekeable space in
 the preamble?

Move the coursor near to a thin space.

Open a source view with ViewSource, (eventually select output format LaTeX).

Have a look at the LaTeX command in place of the thin space: Is it \, or
\thinspace?

In the preamble write something like

  \renewcommand{\thinspace}{\kern .13em }

Try, whether this definition is still no-break.

Günter

Re: thinspace too wide

[Guenter Milde]

On 2014-02-04, Jürgen Spitzmüller wrote:

 [-- Type: text/plain, Encoding: quoted-printable --]

 2014-02-04 Marcelo Acuña marceloacu...@yahoo.com:

 hello
  I want to get control over wide of thinspace.
  The present is too wide.


 The original definition is
 \def\thinspace{\kern .16667em }

 go change it in the preamble.


  Plus I want that thinspace make a hard link between parts and not be
 broken by hypenation.

 This I don't understand.

I suppose the OP is looking for a non-breaking thin space

202FNARROW NO-BREAK SPACE
* commonly abbreviated NNBSP
* a narrow form of a no-break space, typically the width of a thin 
space or a mid space
x (no-break space - 00A0)
x (four-per-em space - 2005)
x (thin space - 2009)
# noBreak 0020


LyX's unicodesymbols Unicode-LaTeX conversion file says:

0x202f \\,\\,  # NARROW NO-BREAK SPACE

So, Marcelo, you can either input the unicode character 
or (as ERT/raw latex) the command \, 
or redefine \thinspace in the preamble to be \,

Günter

Re: thinspace too wide

[Guenter Milde]

On 2014-02-05, Marcelo Acuña wrote:

 [-- Type: text/plain, Encoding: quoted-printable --]

 OK Guenter, and, How I can redefine de narrow non-brekeable space in
 the preamble?

Move the coursor near to a thin space.

Open a source view with ViewSource, (eventually select output format LaTeX).

Have a look at the LaTeX command in place of the thin space: Is it \, or
\thinspace?

In the preamble write something like

  \renewcommand{\thinspace}{\kern .13em }

Try, whether this definition is still no-break.

Günter

Re: thinspace too wide

[Guenter Milde]

On 2014-02-04, Jürgen Spitzmüller wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> 2014-02-04 Marcelo Acuña :

>> hello
>>  I want to get control over wide of thinspace.
>>  The present is too wide.


> The original definition is
> \def\thinspace{\kern .16667em }

> go change it in the preamble.


>>  Plus I want that thinspace make a hard link between parts and not be
>> broken by hypenation.

> This I don't understand.

I suppose the OP is looking for a non-breaking thin space

202FNARROW NO-BREAK SPACE
* commonly abbreviated NNBSP
* a narrow form of a no-break space, typically the width of a thin 
space or a mid space
x (no-break space - 00A0)
x (four-per-em space - 2005)
x (thin space - 2009)
#  0020


LyX's "unicodesymbols" Unicode->LaTeX conversion file says:

0x202f "\\,"  "" "" "\\," "" # NARROW NO-BREAK SPACE

So, Marcelo, you can either input the unicode character 
or (as ERT/raw latex) the command \, 
or redefine \thinspace in the preamble to be \,

Günter

Re: thinspace too wide

[Guenter Milde]

On 2014-02-05, Marcelo Acuña wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> OK Guenter, and, How I can redefine de narrow non-brekeable space in
> the preamble?

Move the coursor near to a thin space.

Open a "source view" with View>Source, (eventually select output format LaTeX).

Have a look at the LaTeX command in place of the thin space: Is it \, or
\thinspace?

In the preamble write something like

  \renewcommand{\thinspace}{\kern .13em }

Try, whether this definition is still "no-break".

Günter

Re: using native 'math macros' as 'text macros'

[Guenter Milde]

On 2014-01-22, Liviu Andronic wrote:

 So, is it a good or bad idea to use math macros to emulate text
 macros? Is there a nicer approach?

IMO, it is a bad idea. Math macros are for mathematical typesetting (and
even then not the cleanest LaTeX code results).

The text alternative to math macros are insets. You could define them
either in a custom layout, a module or a local layout.

Günter

Re: using native 'math macros' as 'text macros'

[Guenter Milde]

On 2014-01-22, Liviu Andronic wrote:

 So, is it a good or bad idea to use math macros to emulate text
 macros? Is there a nicer approach?

IMO, it is a bad idea. Math macros are for mathematical typesetting (and
even then not the cleanest LaTeX code results).

The text alternative to math macros are insets. You could define them
either in a custom layout, a module or a local layout.

Günter

Re: using native 'math macros' as 'text macros'

[Guenter Milde]

On 2014-01-22, Liviu Andronic wrote:

> So, is it a good or bad idea to use math macros to emulate text
> macros? Is there a nicer approach?

IMO, it is a bad idea. "Math macros" are for mathematical typesetting (and
even then not the cleanest LaTeX code results).

The text alternative to "math macros" are "insets". You could define them
either in a custom layout, a module or a local layout.

Günter

Re: Openning files created in Lyx 2.1 on Lyx 2.0.6

[Guenter Milde]

On 2014-01-03, Zorig Davaanyam wrote:

 Hi all,

 I can't open files created in Lyx 2.1 on Lyx 2.0.6.
 The following error shows up.

 C:/Users/Zorig/AppData/Local/Temp/lyx_tmpdir.Hp5464/Buffer_convertLyxFormat.XX
 is not a readable Lyx document.

 My system is Windows 8 64bit.

 Please help me to fix this error.

This is normal behaviour. LyX files are compatible only in one direction.

You can export files in 2.0.x-format with 2.1
and you can read 2.0.x files with 2.1. The advantorous can also replace the
lyx2lyx.py script from 2.0 with the 2.1 one and get auto-conversion in both
directions.

Günter

Re: Openning files created in Lyx 2.1 on Lyx 2.0.6

[Guenter Milde]

On 2014-01-03, Zorig Davaanyam wrote:

 Hi all,

 I can't open files created in Lyx 2.1 on Lyx 2.0.6.
 The following error shows up.

 C:/Users/Zorig/AppData/Local/Temp/lyx_tmpdir.Hp5464/Buffer_convertLyxFormat.XX
 is not a readable Lyx document.

 My system is Windows 8 64bit.

 Please help me to fix this error.

This is normal behaviour. LyX files are compatible only in one direction.

You can export files in 2.0.x-format with 2.1
and you can read 2.0.x files with 2.1. The advantorous can also replace the
lyx2lyx.py script from 2.0 with the 2.1 one and get auto-conversion in both
directions.

Günter

Re: Openning files created in Lyx 2.1 on Lyx 2.0.6

[Guenter Milde]

On 2014-01-03, Zorig Davaanyam wrote:

> Hi all,

> I can't open files created in Lyx 2.1 on Lyx 2.0.6.
> The following error shows up.

> C:/Users/Zorig/AppData/Local/Temp/lyx_tmpdir.Hp5464/Buffer_convertLyxFormat.XX
> is not a readable Lyx document.

> My system is Windows 8 64bit.

> Please help me to fix this error.

This is normal behaviour. LyX files are compatible only in one direction.

You can export files in 2.0.x-format with 2.1
and you can read 2.0.x files with 2.1. The advantorous can also replace the
lyx2lyx.py script from 2.0 with the 2.1 one and get auto-conversion in both
directions.

Günter

Re: automatic equation numbering

[Guenter Milde]

On 2013-12-20, Patrick Dupre wrote:
 Hello,

 Is there an option to have all the equations automatically numbered if
 I only label some of them ?

For this, I have in my latex preamble:

% Gleichungen
% ---
% Alle Gleichungen nummerieren
\renewcommand\[{\begin{equation}}
\renewcommand\]{\end{equation}}

And additionally to number by chapter (do not add this if you want
consecutive numbering over the whole document):

% Starte Gleichungsnummern für jedes Kapitel neu (mit AMS mathe)
\numberwithin{equation}{chapter}


Günter

Re: automatic equation numbering

[Guenter Milde]

On 2013-12-20, Patrick Dupre wrote:
 Hello,

 Is there an option to have all the equations automatically numbered if
 I only label some of them ?

For this, I have in my latex preamble:

% Gleichungen
% ---
% Alle Gleichungen nummerieren
\renewcommand\[{\begin{equation}}
\renewcommand\]{\end{equation}}

And additionally to number by chapter (do not add this if you want
consecutive numbering over the whole document):

% Starte Gleichungsnummern für jedes Kapitel neu (mit AMS mathe)
\numberwithin{equation}{chapter}


Günter

Re: automatic equation numbering

[Guenter Milde]

On 2013-12-20, Patrick Dupre wrote:
> Hello,

> Is there an option to have all the equations automatically numbered if
> I only label some of them ?

For this, I have in my "latex preamble":

% Gleichungen
% ---
% Alle Gleichungen nummerieren
\renewcommand\[{\begin{equation}}
\renewcommand\]{\end{equation}}

And additionally to number by chapter (do not add this if you want
consecutive numbering over the whole document):

% Starte Gleichungsnummern für jedes Kapitel neu (mit AMS mathe)
\numberwithin{equation}{chapter}


Günter

Re: Koma(book) question

[Guenter Milde]

On 2013-12-19, Dr Eberhard Lisse wrote:
 Auntie Google is your friend.
 Look for latex section titles ie

Generally a good idea. In this case, the search term should include KOMA.

The KOMA classes include tools for custimization that work differently from
titlesec and do not work especially well together. So generally use either
KOMA-script classes (and read scrguide.pdf or scrguien.pdf) or titlesec
(and read its documentation) but not both.

Günter

Re: pdflatex font problem

[Guenter Milde]

On 2013-12-18, ZhuHao wrote:

 [-- Type: text/plain, Encoding: base64 --]

 After using pdflatex (or luatex for that matter)

It does matter a lot, whether you use pdflatex or lualatex, even with
lualatex in 8-bit emulation mode (there are differences caused by bugs in
LyX and babel-greek).

Changing DocumentSettingsFontsFont-encoding to LGR,T1 may help.

 , when printing my Lyx
 document to the printer the greek \alpha character is missing from the
 printed (or pre-printed) pdf document. I know it has something to do
 with fontloading into the document but don't know how to resolve it.
 Exporting to latex proper followed by dvipdf works fine... I'm using
 Linux/Debian. Help much appreciated! Thanks.

We need more info:

Do you use Greek in text or mathematical mode?

Do other Greek characters fail, too? 
Do the uppercase Greek characters fail?

What is the font setting (default, custom, ...)

Does the alpha show in a pdf previewer?

Does it also fail with ViewPDF (pdflatex)?

Does it also fail with export and compilation with pdflatex?

Günter

Re: Koma(book) question

[Guenter Milde]

On 2013-12-19, Dr Eberhard Lisse wrote:
 Auntie Google is your friend.
 Look for latex section titles ie

Generally a good idea. In this case, the search term should include KOMA.

The KOMA classes include tools for custimization that work differently from
titlesec and do not work especially well together. So generally use either
KOMA-script classes (and read scrguide.pdf or scrguien.pdf) or titlesec
(and read its documentation) but not both.

Günter

Re: pdflatex font problem

[Guenter Milde]

On 2013-12-18, ZhuHao wrote:

 [-- Type: text/plain, Encoding: base64 --]

 After using pdflatex (or luatex for that matter)

It does matter a lot, whether you use pdflatex or lualatex, even with
lualatex in 8-bit emulation mode (there are differences caused by bugs in
LyX and babel-greek).

Changing DocumentSettingsFontsFont-encoding to LGR,T1 may help.

 , when printing my Lyx
 document to the printer the greek \alpha character is missing from the
 printed (or pre-printed) pdf document. I know it has something to do
 with fontloading into the document but don't know how to resolve it.
 Exporting to latex proper followed by dvipdf works fine... I'm using
 Linux/Debian. Help much appreciated! Thanks.

We need more info:

Do you use Greek in text or mathematical mode?

Do other Greek characters fail, too? 
Do the uppercase Greek characters fail?

What is the font setting (default, custom, ...)

Does the alpha show in a pdf previewer?

Does it also fail with ViewPDF (pdflatex)?

Does it also fail with export and compilation with pdflatex?

Günter

Re: Koma(book) question

[Guenter Milde]

On 2013-12-19, Dr Eberhard Lisse wrote:
> Auntie Google is your friend.
> Look for latex "section titles" ie

Generally a good idea. In this case, the search term should include "KOMA".

The KOMA classes include tools for custimization that work differently from
"titlesec" and do not work especially well together. So generally use either
KOMA-script classes (and read "scrguide.pdf" or scrguien.pdf") or "titlesec"
(and read its documentation) but not both.

Günter

Re: pdflatex font problem

[Guenter Milde]

On 2013-12-18, ZhuHao wrote:

> [-- Type: text/plain, Encoding: base64 --]

> After using pdflatex (or luatex for that matter)

It does matter a lot, whether you use pdflatex or lualatex, even with
lualatex in 8-bit emulation mode (there are differences caused by bugs in
LyX and babel-greek).

Changing Document>Settings>Fonts>Font-encoding to LGR,T1 may help.

> , when printing my Lyx
> document to the printer the greek \alpha character is missing from the
> printed (or pre-printed) pdf document. I know it has something to do
> with fontloading into the document but don't know how to resolve it.
> Exporting to latex proper followed by dvipdf works fine... I'm using
> Linux/Debian. Help much appreciated! Thanks.

We need more info:

Do you use Greek in text or mathematical mode?

Do other Greek characters fail, too? 
Do the uppercase Greek characters fail?

What is the font setting (default, custom, ...)

Does the alpha show in a pdf previewer?

Does it also fail with View>PDF (pdflatex)?

Does it also fail with export and compilation with pdflatex?

Günter

Re: Comment écrire en Quôc Ngu' avec LyX ?

[Guenter Milde]

On 2013-12-18, Liviu Andronic wrote:
 2013/12/18 Julien Rioux jri...@lyx.org:
 Robert is asking how to write vietnamese using LyX. He says he doesn't
 succeed in using X-Unikey under Linux, whereas he could use it under Windows
 (but, reading between the lines, he would rather not use Windows OS).
 Normally, one should be able to write in any language with LyX, and
 vietnamese is an alphabetical language.

 Well, we do have this wiki page:
 http://wiki.lyx.org/Windows/Vietnamese . Since 1.6 we seem to support
 Vietnamese: http://wiki.lyx.org/LyX/NewInLyX16#toc12 .

 Maybe the user needs to install VnTeX on Linux (or whatever), but I
 have no experience with this.

There are several issues:

input: LyX understands Unicode, so every input that works with other
   programs should work with LyX, too.

language environment: For typesetting with TeX, you need the vietnamese
   support for Babel or Polyglossia
   
fonts: The Latin script used in Vietnameese has some special accented
   characters:

   With 8-bit TeX, you need specially encoded fonts - they usually come
   wiht the distributions texlive-vietnamese support package.
   
   With XeTeX/LuaTeX, any system font that has the required characters
   can be used.
   
   
Günter

Re: Comment écrire en Quôc Ngu' avec LyX ?

[Guenter Milde]

On 2013-12-18, Liviu Andronic wrote:
 2013/12/18 Julien Rioux jri...@lyx.org:
 Robert is asking how to write vietnamese using LyX. He says he doesn't
 succeed in using X-Unikey under Linux, whereas he could use it under Windows
 (but, reading between the lines, he would rather not use Windows OS).
 Normally, one should be able to write in any language with LyX, and
 vietnamese is an alphabetical language.

 Well, we do have this wiki page:
 http://wiki.lyx.org/Windows/Vietnamese . Since 1.6 we seem to support
 Vietnamese: http://wiki.lyx.org/LyX/NewInLyX16#toc12 .

 Maybe the user needs to install VnTeX on Linux (or whatever), but I
 have no experience with this.

There are several issues:

input: LyX understands Unicode, so every input that works with other
   programs should work with LyX, too.

language environment: For typesetting with TeX, you need the vietnamese
   support for Babel or Polyglossia
   
fonts: The Latin script used in Vietnameese has some special accented
   characters:

   With 8-bit TeX, you need specially encoded fonts - they usually come
   wiht the distributions texlive-vietnamese support package.
   
   With XeTeX/LuaTeX, any system font that has the required characters
   can be used.
   
   
Günter

Re: Comment écrire en Quôc Ngu' avec LyX ?

[Guenter Milde]

On 2013-12-18, Liviu Andronic wrote:
> 2013/12/18 Julien Rioux :
>> Robert is asking how to write vietnamese using LyX. He says he doesn't
>> succeed in using X-Unikey under Linux, whereas he could use it under Windows
>> (but, reading between the lines, he would rather not use Windows OS).
>> Normally, one should be able to write in any language with LyX, and
>> vietnamese is an alphabetical language.

> Well, we do have this wiki page:
> http://wiki.lyx.org/Windows/Vietnamese . Since 1.6 we seem to support
> Vietnamese: http://wiki.lyx.org/LyX/NewInLyX16#toc12 .

> Maybe the user needs to install VnTeX on Linux (or whatever), but I
> have no experience with this.

There are several issues:

input: LyX understands Unicode, so every input that works with other
   programs should work with LyX, too.

language environment: For typesetting with TeX, you need the vietnamese
   support for Babel or Polyglossia
   
fonts: The Latin script used in Vietnameese has some special accented
   characters:

   With 8-bit TeX, you need specially encoded fonts - they usually come
   wiht the distributions texlive-vietnamese support package.
   
   With XeTeX/LuaTeX, any system font that has the required characters
   can be used.
   
   
Günter

Re: inter-item and inter-paragraph spacing

[Guenter Milde]

On 2013-12-12, mike wrote:

 I have a document which almost entirely consists of nested enumerated 
 lists.  The problem is that the vertical spacing between paragraphs and 
 items in an enumerated list is too close together.  I have tried to 
 remedy this in Document  Settings  Text Layout by using the vertical 
 space button but that doesn't seem to have any effect.  In the same 
 dialogue box if I set line spacing to double I almost get what I want 
 except that individual paragraphs are double spaced.  What I really want 
 is that everything is double spaced except for the lines in an 
 individual paragraph.

For separating of items in a list, use is Enumitem LyX module. It makes
use of package enumitem. Now insert the LaTeX code for configuration of
the list-item-separting space in DocumentSettingsLaTeX preamble. Read
ftp://tug.ctan.org/pub/tex-archive/macros/latex/contrib/enumitem/enumitem.pdf
for details.

For separating paragraphs by vertical space instead of indent, use the
package parskip. (\usepackage{parskip} in the LaTeX preamble).

Günter

Re: inter-item and inter-paragraph spacing

[Guenter Milde]

On 2013-12-12, mike wrote:

 I have a document which almost entirely consists of nested enumerated 
 lists.  The problem is that the vertical spacing between paragraphs and 
 items in an enumerated list is too close together.  I have tried to 
 remedy this in Document  Settings  Text Layout by using the vertical 
 space button but that doesn't seem to have any effect.  In the same 
 dialogue box if I set line spacing to double I almost get what I want 
 except that individual paragraphs are double spaced.  What I really want 
 is that everything is double spaced except for the lines in an 
 individual paragraph.

For separating of items in a list, use is Enumitem LyX module. It makes
use of package enumitem. Now insert the LaTeX code for configuration of
the list-item-separting space in DocumentSettingsLaTeX preamble. Read
ftp://tug.ctan.org/pub/tex-archive/macros/latex/contrib/enumitem/enumitem.pdf
for details.

For separating paragraphs by vertical space instead of indent, use the
package parskip. (\usepackage{parskip} in the LaTeX preamble).

Günter

Re: inter-item and inter-paragraph spacing

[Guenter Milde]

On 2013-12-12, mike wrote:

> I have a document which almost entirely consists of nested enumerated 
> lists.  The problem is that the vertical spacing between paragraphs and 
> items in an enumerated list is too close together.  I have tried to 
> remedy this in Document > Settings > Text Layout by using the vertical 
> space button but that doesn't seem to have any effect.  In the same 
> dialogue box if I set line spacing to double I almost get what I want 
> except that individual paragraphs are double spaced.  What I really want 
> is that everything is "double spaced" except for the lines in an 
> individual paragraph.

For separating of items in a list, use is Enumitem LyX module. It makes
use of package enumitem. Now insert the LaTeX code for configuration of
the list-item-separting space in Document>Settings>LaTeX preamble. Read
ftp://tug.ctan.org/pub/tex-archive/macros/latex/contrib/enumitem/enumitem.pdf
for details.

For separating paragraphs by vertical space instead of indent, use the
package parskip. (\usepackage{parskip} in the LaTeX preamble).

Günter