Re: lyx to latex

[Andrew Parsloe]

On 20/03/2017 2:22 p.m., John White wrote:

Apparently. At least I don't see it in lyx 2.2.2.

We are required occasionally by a court to submit proposed orders in
microsoft word. These are on pleading paper. Easy to prepare the order
in lyx but in exporting it to microsoft it loses the line numbers.
Libreoffice and openoffice do a better job, but when exporting from
either libreoffice or openoffice to .doc, the line numbers are also lost.

I can't recall if I had this problem when we could export directly from
lyx to rtf, but I don't think so.

John

On Monday, March 20, 2017 1:12:03 AM PDT Patrick Dupre wrote:

 > Hello,

 >

 > If I remember correctly, I was able to convert directly a lyx file to a

 > rtf file in the past. Did this option disappear ?

 >

 > Thank.

 >

 >
===

 > Patrick DUPRÉ | | email: pdu...@gmx.com

 > Laboratoire de Physico-Chimie de l'Atmosphère | |

 > Université du Littoral-Côte d'Opale | |

 > Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44

 > 189A, avenue Maurice Schumann | | 59140 Dunkerque, France

 >
===

I'm on windows, so the detail will be different, but I can export 
directly from LyX 2.2.2 to rtf. I had to set up the converter myself, 
using latex2rtf. In Tools > Preferences > File Handling > Converters I 
have a converter from LaTeX (plain) to Rich Text Format (so LyX exports 
first to LaTeX then from LaTeX to rtf) and in the Converter slot I have


c:/progra~2/latex2rtf/latex2rt.exe -P c:progra~2/latex2rtf/cfg $$i

latex2rtf is installed at "C:/Program Files (x86)/latex2rtf". The 
"c:/progra~2" is the windows way of coping with the spaces in 
"C:/Program Files (x86)".


(The export works; latex2rtf has got better over the years.)

Andrew




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: lyx to latex

[Kornel Benko]

Am Montag, 20. März 2017 um 18:38:20, schrieb Guenter Milde 
> On 2017-03-20, Patrick Dupre wrote:
> > Is weird,
> 
> Indeed.
> 
> > In preference, I have:
> 
> > From format lyx to format reach text Font:
> 
> > 'latex2rtf -p -S -o $$o $$i'
> 
> To "text Font"?
> 
> Which "preference" file?
> 
> Is latex2rtf in your PATH?
> 
> > But when I export it does a pdflatex
> 
> How do you start the export?
> 
> Günter
> 

Don't know if this may be your problem too. Just downloaded tar
from sourceforge. Compiled, installed.
The converter is not working as long as using '-o $$o'.

Debugging led me to this snippet in latex2rtf-2.3.12/main.c:366

if (g_rtf_name == NULL) {
g_rtf_name = strdup_together3(g_home_dir,basename,".rtf");
} else if (g_rtf_name = g_tex_name) {
diagnostics(ERROR, "rtf file must be different from tex file");
}

which clearly is wrong. (line 368 should be: '} else if (g_rtf_name == 
g_tex_name) {')

Patching this file and now this converter works.

Kornel


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

Re: Conversion Problem

[subhuman]

On Sat, 18 Mar 2017 15:19:19 + (UTC)
Guenter Milde  wrote:

> > after upgrading LyX from version 2.1.4 to 2.2.2, paragraphs in a
> > 2.1-document are no longer recognized. 
> 
> Does this mean several paragraphs are
No, nothing of the content seems to be missing, except the linebreaks ending 
one paragraph and starting the next one.
> 
> * missing in the GUI / in the output
Only in the output. In the GUI everything looks as it should, except for 
pagebreak/ newpage markers. But that's probably a minor problem and can be 
fixed via "View".
> 
> * merged into one in the GUI / output
Only in the output. The whole text appears in one single paragraph.
> 
> 
> Does the same unwanted effect happen with a new document?
I'm unable to tell, because in want to have a working application I downgraded 
back to the earlier version of LyX.
> 
> Does it affect more than one document?
See above.

Since the effect only appears in the output I fancy the failure might lay in 
changes in the way LyX reads and interprets layouts. I've attached the layout 
file in question to this message. 

> 
> > How can I convince the new and probably much better LyX to recognize
> > again what it once did?
> 
> This, we may tell if you provide a *minimal* example - i.e. the smallest
> possible excerpt that produces the unwanted effect.
> 
> Günter
> 


-- 
The world is such a nasty place to be.
#% Do not delete the line below; configure depends on this
# \DeclareLaTeXClass[book]{book (Keuchhusten)}

Format 35

ClassOptions
  PageStyle plain
End

###
# basic definitions, adopted from stdclass.inc -
# however, that include calls too many other inc's
# we won't need.

Columns 1
Sides   1   # change me!
SecNumDepth 1
TocDepth1
DefaultStyleStandard

DefaultFont
  FamilyRoman
  SeriesMedium
  Shape Up
  Size  Normal
  Color Black
EndFont

Style Standard
  Category  MainText
  MarginStatic
  LatexType Paragraph
  NextNoIndent  0
  KeepEmpty 1
  ParIndent MM
  ParSkip   0
  ParbreakIsNewline 1
  TopSep0
  BottomSep 0.5
  Align Block
  AlignPossible Block
  LabelType No_Label
  HTMLStyle div.standard {
margin-bottom: 0px;
}
  EndHTMLStyle
End

Style StandardFirst
  CopyStyle Standard
  KeepEmpty 0
  ParIndent ""
  BottomSep 0
  NextNoIndent  0
End

Style Poem_(Verse)
  CopyStyle Standard
  ParIndent 
  Align Left
  AlignPossible Left
End

Style Poem_(Stanza)
  CopyStyle StandardFirst
  ParIndent 
  Align Left
  AlignPossible Left
End


###
# the same, now from stdlayouts.inc - we could as
# well CopyStyle from Quotation, but then we'd have
# to live with an element in the dropdown menu we
# don't need. hence, for the sake of perfection, 
# we go on foot.

Style Letter_handwritten
  Category  MainText
  MarginStatic
  LatexType Environment
  LatexName quotation
  NextNoIndent  1
  LeftMarginMM
  RightMargin   MM
  ParIndent ""
  ParSkip   0
  ItemSep   0
  TopSep0
  BottomSep 0.5
  ParSep0
  FreeSpacing   1
  Newline   1
  Font
Family  Roman
Shape   Italic
  EndFont
  Align Left
  AlignPossible Left, Right
  HTMLTag   blockquote
  HTMLItem  div
  
End

Style Letter_typed
  CopyStyle Letter_handwritten
  Font
Family  Typewriter
Shape   Up
  EndFont
End

###
# modifications to existing definitions
# -
Input stdtitle.inc

Style Title
  Font
Sizehuge
Series  bold
  EndFont
End

NoStyle Date
# end stdtitle.inc

# -
Input stdcounters.inc

Counter chapter
  LabelString   "\Roman{chapter}"
End
# end stdcounters.inc

# -
Input stdsections.inc

NoStyle Subparagraph
NoStyle Paragraph
NoStyle Subsubsection
NoStyle Subsection
NoStyle Section
NoStyle Part

Style Chapter
  LatexType Command
  LatexName mychapter
  LabelType Counter
  LabelCounter  chapter
  LabelString   "\thechapter"
  Align center
  AlignPossible   

RE: Missing glyphs! Missing character: There is no , (U+2028) in font [XXX]:mode=node;s

[Bernt Lie]

-Original Message-
From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
jezZiFeR
Sent: søndag 19. mars 2017 16.28
To: lyx-users@lists.lyx.org
Subject: Missing glyphs! Missing character: There is no , (U+2028) in font 
[XXX]:mode=node;s



Hello,



I have a problem with LuaTeX / XeTeX



LyX 2.2.2

OS Sierra 10.12

LuaTeX, freshly updated



No matter which font I chhose, I always get the message »Missing

character: There is no (U+2028) in font [whichever]:mode=node;s«. I choose to 
show the output nonetheless several times, because the error-message keeps 
showing. With some fonts the italics are not displayed, in some cases the 
resulting PDF seems to be correct at first sight. The fonts seem to be 
correctly installed.



The same happens with XeTeX also.



Does anybody know what might be wrong here? I have seen a very close, but not a 
similar question in the archive:

http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg196621.html

That’s why I ask here. Hope, somebody could help.



Thanks

Jess

--

Not completely related, but I get a "Missing glyphs!" (two times) with LyX 
2.2.2 on Windows 10. The source of this missing glyphs are two occurrences of 
BibTeX references containing the character {\AA} (I assume this is the source – 
the error message showed up after I included these references…).

 [cid:image001.png@01D2A157.2A66E9E0]

In JabRef:

[cid:image002.png@01D2A157.62DA8340]



JabRef details:

[cid:image003.png@01D2A157.62DA8340]



The result still looks ok in the reference list, though:

[cid:image004.png@01D2A157.B6D16A90]



I’m not quite sure of how to fix this, i.e., avoid the error message/warning in 
LyX 2.2.2.



Thanks,

Bernt

Re: lyx to latex

[Patrick Dupre]

Is weird,

In preference, I have:
>From format lyx to format reach text Font:
'latex2rtf -p -S -o $$o $$i'

But when I export it does a pdflatex


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Monday, March 20, 2017 at 12:18 PM
> From: "Guenter Milde" 
> To: lyx-users@lists.lyx.org
> Subject: Re: lyx to latex
>
> On 2017-03-20, Patrick Dupre wrote:
> > Hello,
> 
> > If I remember correctly, I was able to convert directly a lyx file to a
> > rtf file in the past. Did this option disappear ?
> 
> It seems to be still in LyX but depends on the external program latex2rtf:
> 
> configure.py contains the code:
> 
> checkProg('a LaTeX -> RTF converter', ['latex2rtf -p -S -o $$o $$i', 
> 'latex2rt -p -S -o $$o $$i'],
> rc_entry = [ r'\converter latex  rtf"%%"  "needaux"' ])
> 
> Günter
> 
> 
>

RE: Missing glyphs! Missing character: There is no , (U+2028) in font [XXX]:mode=node;s

[Bernt Lie]

-Original Message-
From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
Guenter Milde
Sent: mandag 20. mars 2017 10.16
To: lyx-users@lists.lyx.org
Subject: Re: Missing glyphs! Missing character: There is no , (U+2028) in font 
[XXX]:mode=node;s

On 2017-03-20, Bernt Lie wrote:

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

> -Original Message-
> From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On 
> Behalf Of jezZiFeR
> Sent: søndag 19. mars 2017 16.28
> To: lyx-users@lists.lyx.org
> Subject: Missing glyphs! Missing character: There is no , (U+2028) in 
> font [XXX]:mode=node;s



> I have a problem with LuaTeX / XeTeX

> No matter which font I chhose, I always get the message »Missing

> character: There is no (U+2028) in font [whichever]:mode=node;s«.

This character is the line separator. The error message can be safely ignored.

The same holds for 0x200c  ZERO WIDTH NON-JOINER (a missing character has the 
same effect (preventing ligatures and kerning)

and maybe some other nonprintable characters. I suggest an exception list for 
the missing-characters-warning-to-error feature.



> I choose to show the output nonetheless several times, because the 
> error-message keeps showing. With some fonts the italics are not 
> displayed, in some cases the resulting PDF seems to be correct at 
> first sight. The fonts seem to be correctly installed.

This is unrelated.

...


> Not completely related, but I get a "Missing glyphs!" (two times) with 
> LyX 2.2.2 on Windows 10. The source of this missing glyphs are two 
> occurrences of BibTeX references containing the character {\AA} (I 
> assume this is the source – the error message showed up after I 
> included these references…).

The latex macro \AA is translated to 

212BANGSTROM SIGN
* non SI length unit (=0.1 nm) named after A. J. Ångström, Swedish 
physicist

The Unicode standard says:

* preferred representation is 00C5

00C5LATIN CAPITAL LETTER A WITH RING ABOVE

Both character look the same but some fonts only contain 00C5.

You can solve this by changing \AA to \r{A} in the bibtex file or by selecting 
a font with 212B.

Günter
--
Hm. The LaTeX macro \AA *should* be translated to the Scandinavian letter Å, at 
least according to some LaTeX manuals I have read through the years. As in 
Ångström (Swedish name) or Årdal (Norwegian name). Danes tend to use Aa instead 
of Å, but the Danish alphabet includes Å.

I tried the suggestion of replacing \AA with \r{A}. Result?
* The typesetting in the bibliography is correct and the same as for when I 
used \AA
* I still get the same missing glyphs message
* Now, I cannot search for Å in JabRef -- if I use \AA, I can search for Å in 
JabRef.

-B

Re: Conversion Problem

[Guenter Milde]

On 2017-03-20, subhuman wrote:
> On Sat, 18 Mar 2017 15:19:19 + (UTC)
> Guenter Milde  wrote:

>> > after upgrading LyX from version 2.1.4 to 2.2.2, paragraphs in a
>> > 2.1-document are no longer recognized. 

>> Does this mean several paragraphs are
...

>> * merged into one in the GUI / output
> Only in the output. The whole text appears in one single paragraph.

OK.

>> Does the same unwanted effect happen with a new document?
> I'm unable to tell, because in want to have a working application I
> downgraded back to the earlier version of LyX.

>> Does it affect more than one document?
> See above.

Where? I can't find any mention of this.

> Since the effect only appears in the output I fancy the failure might
> lay in changes in the way LyX reads and interprets layouts. 

This depends, it may be the layout (if the failure is specific to all
documents using a specific layout) or a specific document or configuration...

> I've attached the layout file in question to this message. 

Thanks.

I see some differences comparing your custom keuchusten layout and the
current standard ones:

* version: 35  vs. 63

* in keuchusten:Standard
 
   ParbreakIsNewline 1

  missing in standard:Standard
  
I suggest, in order to be up-to-date to mimic a standard book layout and
instead of


  # basic definitions, adopted from stdclass.inc -
  # however, that include calls too many other inc's
  # we won't need.

and

  # the same, now from stdlayouts.inc - we could as
  # well CopyStyle from Quotation, but then we'd have
  # to live with an element in the dropdown menu we
  # don't need. hence, for the sake of perfection,
  # we go on foot.

use the same method as in handling stdsections --- delete unwanted style with
NoStyle.

After converting your custom layout this way, you may try again with LyX 2.2.
(There is a way to instal different lyx versions side-by-side...)

Günter

BibTeX + self-edited bibliography…

[jezZiFeR]

Hello,

up to now I only used BibTeX-bibliographies in LyX. Now I would like to 
add titles to the bibliography, which I did not mention in the article. 
Is there a way to do that? It would not mind to have the unmentioned 
entries in a separate paragraph. Would be very helpful…


All best
Jess

LyX layout color customization

[Csaba Pusztai]

Hi,

Based on the documentation (Customizing Lyx: Features for the Advanced User), 
only a handful of pre-defined colors are available for use in layout files. The 
color of some elements are flexibly changeable (full RGB), but in style 
declarations only the named colors are available. Is there any way to work 
around that? If nothing else, could I somehow re-define the named colours?

-- 
Csaba Pusztai
Sent with Airmail

Re: lyx to latex

[Guenter Milde]

On 2017-03-20, Patrick Dupre wrote:
> Hello,

> If I remember correctly, I was able to convert directly a lyx file to a
> rtf file in the past. Did this option disappear ?

It seems to be still in LyX but depends on the external program latex2rtf:

configure.py contains the code:

checkProg('a LaTeX -> RTF converter', ['latex2rtf -p -S -o $$o $$i', 
'latex2rt -p -S -o $$o $$i'],
rc_entry = [ r'\converter latex  rtf"%%""needaux"' ])

Günter

Re: Missing glyphs! Missing character: There is no , (U+2028) in font [XXX]:mode=node;s

[Guenter Milde]

On 2017-03-20, Bernt Lie wrote:

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

> -Original Message-
> From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
> jezZiFeR
> Sent: søndag 19. mars 2017 16.28
> To: lyx-users@lists.lyx.org
> Subject: Missing glyphs! Missing character: There is no , (U+2028) in font 
> [XXX]:mode=node;s



> I have a problem with LuaTeX / XeTeX

> No matter which font I chhose, I always get the message »Missing

> character: There is no (U+2028) in font [whichever]:mode=node;s«.

This character is the line separator. The error message can be safely ignored.

The same holds for 0x200c  ZERO WIDTH NON-JOINER (a missing character has
the same effect (preventing ligatures and kerning)

and maybe some other nonprintable characters. I suggest an exception list
for the missing-characters-warning-to-error feature.



> I choose to show the output nonetheless several times, because the
> error-message keeps showing. With some fonts the italics are not
> displayed, in some cases the resulting PDF seems to be correct at first
> sight. The fonts seem to be correctly installed.

This is unrelated.

...


> Not completely related, but I get a "Missing glyphs!" (two times) with
> LyX 2.2.2 on Windows 10. The source of this missing glyphs are two
> occurrences of BibTeX references containing the character {\AA} (I
> assume this is the source – the error message showed up after I
> included these references…).

The latex macro \AA is translated to 

212BANGSTROM SIGN
* non SI length unit (=0.1 nm) named after A. J. Ångström, Swedish 
physicist

The Unicode standard says:

* preferred representation is 00C5

00C5LATIN CAPITAL LETTER A WITH RING ABOVE

Both character look the same but some fonts only contain 00C5.

You can solve this by changing \AA to \r{A} in the bibtex file or by
selecting a font with 212B.

Günter

Re: BibTeX + self-edited bibliography…

[Jürgen Spitzmüller]

2017-03-20 13:59 GMT+01:00 jezZiFeR :

> Hello,
>
> up to now I only used BibTeX-bibliographies in LyX. Now I would like to
> add titles to the bibliography, which I did not mention in the article. Is
> there a way to do that?


Yes, use \nocite* (or in the citation dialog: "Add to bibliography only"
for the respective references).


> It would not mind to have the unmentioned entries in a separate paragraph.
> Would be very helpful…
>

This can be done with the "Sectioned Bibliography" feature. It is described
in the LyX manuals.

HTH
Jürgen



>
> All best
> Jess
>

Re: BibTeX + self-edited bibliography…

[jezZiFeR]

Hello Jürgen,

thank you for your message. I did not forget to search the manuals, but 
it did not help: I have entered a bibliography-environment 
(Literaturverzeichnis-Umgebung in german). The manual says:
»Am Anfang der ersten Zeile eines Absatzes werden Sie ein graues 
Kästchen mit einem Wort und einer Zahl in eckigen Klammern sehen.« /
You will see a gray box in the first line of a paragraph with a word and 
a number in square brackets.


In my case just the words »Die Literaturverzeichnis-Umgebung« are 
entered, nothing could be clicked or edited here. I use 
KOMA-Script-Aufsatz, natbib and also a BibDesk-generated bib-file for 
the bibliography.



Maybe this is why I do not understand where to find the citation 
dialogue mentioned. Would that be tha place, in the 
bibliography-environment? I am also not sure where to enter the command. 
The »Sectioned Bibliographies« feature is very useful, thank you.


All best
Jess








Jürgen Spitzmüller 
20. März 2017 um 17:18
2017-03-20 13:59 GMT+01:00 jezZiFeR >:


Hello,

up to now I only used BibTeX-bibliographies in LyX. Now I would
like to add titles to the bibliography, which I did not mention in
the article. Is there a way to do that? 



Yes, use \nocite* (or in the citation dialog: "Add to bibliography 
only" for the respective references).


It would not mind to have the unmentioned entries in a separate
paragraph. Would be very helpful…


This can be done with the "Sectioned Bibliography" feature. It is 
described in the LyX manuals.


HTH
Jürgen


All best
Jess

Re: Missing glyphs! Missing character: There is no , (U+2028) in font [XXX]:mode=node;s

[Guenter Milde]

On 2017-03-20, Bernt Lie wrote:
> On 2017-03-20, Bernt Lie wrote:
>> Sent: søndag 19. mars 2017 16.28

>> I have a problem with LuaTeX / XeTeX


>> Not completely related, but I get a "Missing glyphs!" (two times) with 
>> LyX 2.2.2 on Windows 10. The source of this missing glyphs are two 
>> occurrences of BibTeX references containing the character {\AA} (I 
>> assume this is the source – the error message showed up after I 
>> included these references…).

> The latex macro \AA is translated to 

> 212B  ANGSTROM SIGN
>   * non SI length unit (=0.1 nm) named after A. J. Ångström, Swedish 
> physicist

> The Unicode standard says:

>   * preferred representation is 00C5

> 00C5  LATIN CAPITAL LETTER A WITH RING ABOVE

> Both character look the same but some fonts only contain 00C5.

> You can solve this by changing \AA to \r{A} in the bibtex file or by
> selecting a font with 212B.

> Günter
> --

> Hm. The LaTeX macro \AA *should* be translated to the Scandinavian
> letter Å, at least according to some LaTeX manuals I have read through
> the years. 

* 8-bit TeX does not distinguish Å and Å.

* With xunicode sty, it is LATIN CAPITAL LETTER A WITH RING ABOVE for both:

  \DeclareUTFcharacter[\UTFencname]{x00C5}{\AA}
  \DeclareUTFcomposite[\UTFencname]{x00C5}{\r}{A}

* With tuenc.def \r{A} is Å, too:

  \DeclareTextComposite{\r} \UnicodeEncodingName{A}{"00C5}

  but \AA is not defined.

> As in Ångström (Swedish name) or Årdal (Norwegian name).
Jag vet.

> Danes tend to use Aa instead of Å, but the Danish alphabet includes Å.

Aa is the transkription in case there are no accents (like ue for ü).

> I tried the suggestion of replacing \AA with \r{A}. Result?
> * The typesetting in the bibliography is correct and the same as for
>   when I used \AA

Fine.

> * I still get the same missing glyphs message

Strange. What engine and font do you use?

> * Now, I cannot search for Å in JabRef -- if I use \AA, I can search
>   for Å in JabRef.

This is a JabRef shortcoming. Maybe you can use a literal Å?

Günter

Re: lyx to latex

[Guenter Milde]

On 2017-03-20, Patrick Dupre wrote:
> Is weird,

Indeed.

> In preference, I have:

> From format lyx to format reach text Font:

> 'latex2rtf -p -S -o $$o $$i'

To "text Font"?

Which "preference" file?

Is latex2rtf in your PATH?

> But when I export it does a pdflatex

How do you start the export?

Günter