still be the problem for tex2lyx, because it merges the
equation number (1) with the label to (1k5y). This looks like a bug
in tex2lyx.
Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Scott -
This took me a while because of working with two apps.
Here are a Latex file
MWE.tex
Description: Binary data
and what LyX imports
MWE.lyx
Description: Binary data
. The Lyx file is too short. Also it does not compile because of an extra brace
related to the equation. If you erase th
On Fri, Sep 29, 2023 at 08:28:31AM -0700, Hal Kierstead via lyx-users wrote:
> All -
>
> I have a 1227 line LaTeX file that compiles fine. I would like to import it
> into LyX 2.3.7. Every time I try the import ends at line 543. This is just
> before an \end{proof}. After adding the missing \en
All -
I have a 1227 line LaTeX file that compiles fine. I would like to import it
into LyX 2.3.7. Every time I try the import ends at line 543. This is just
before an \end{proof}. After adding the missing \end{proof} the shortened LyX
file works fine.
I have tried importing other LaTeX files
Jean-Marc
Let's make it
--list-textclasses -l
that was just an example.
The request concerns tex2lyx.
I am getting the available textclasses out of it.
el
n 30/06/2023 11:30, Jean-Marc Lasgouttes wrote:
> Le 30/06/2023 à 11:07, Dr Eberhard Lisse a écrit :
>> so I
[...]
Note that this information is available in /textclasses.lst.
Does this request concern tex2lyx or LyX itself.
I am not totally sure what information you got from it, to be honoest.
JMarc
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Hi,
I am doing an exercise of translating OpenOffice formatted files into
Lyx via pandoc and tex2lyx.
The LyX file is readable but when I use scrlettr it wants Koma Letter V1
which is not installed. I had to do
find /Applications/LyX.app/ -name 'scrl*'
to find
/Ap
pandoc with specific template
do some editing of the LaTeX file with Perl
run tex2lyx
remove ERT with Perl
version the Markdown and LyX file(s)
Review in LyX
Save PDF or print
Now I still need to Train my Dragon to
Perfect, I am an early adopter of new versions so I'll go for 2.4 rather
than for 2.3.[34] anyway.
thanks,
el
On 2019-05-13 18:41 , Jürgen Spitzmüller wrote:
> Am Montag, den 13.05.2019, 14:09 +0200 schrieb Dr Eberhard Lisse:
>> Hi,
>>
>> I have run
>>
>>
Am Montag, den 13.05.2019, 14:09 +0200 schrieb Dr Eberhard Lisse:
> Hi,
>
> I have run
>
> tex2lyx -c scrartcl -m enumitem -f mwe.tex
>
> and get the enclosed
>
> mwe.lyx
>
> where I have manually removed the ERT (see below) from the line with
>
Hi,
I have run
tex2lyx -c scrartcl -m enumitem -f mwe.tex
and get the enclosed
mwe.lyx
where I have manually removed the ERT (see below) from the line with
"item 1" and right clicked that and the line with "item 2" to be proper
Enumerate-Resume which p
o import the a .tex file into LyX (using file->import).
>>>> The file has Turkish characters and I believe it is using UTF8 encoding.
>>>> When I import it, it does not show Turkish characters properly. I
>>>> attached the file for your play-around.
>>>&g
; >> The file has Turkish characters and I believe it is using UTF8 encoding.
> >> When I import it, it does not show Turkish characters properly. I
> >> attached the file for your play-around.
> >>
> >> When I import the file on the command line with the UTF8
import it, it does not show Turkish characters properly. I
>> attached the file for your play-around.
>>
>> When I import the file on the command line with the UTF8 option tex2lyx
>> -e UTF8 ch1.tex, the LyX file looks just fine except one or two characters.
>>
>&g
und.
When I import the file on the command line with the UTF8 option tex2lyx
-e UTF8 ch1.tex, the LyX file looks just fine except one or two characters.
So is there a way to tell to tex2lyx to use UTF8 encoding from within
LyX? This issue is occured when I import a tex file that has
\input{ch1.tex}
; So is there a way to tell to tex2lyx to use UTF8 encoding from within
>> LyX? This issue is occured when I import a tex file that has
>> \input{ch1.tex} in it. So, maybe LyX has and option to force tex2lyx to
>> read in UTF8 for all imports?
>
> THe question is why tex
Le 02/11/2018 à 10:33, Baris Erkus a écrit :
So is there a way to tell to tex2lyx to use UTF8 encoding from within
LyX? This issue is occured when I import a tex file that has
\input{ch1.tex} in it. So, maybe LyX has and option to force tex2lyx to
read in UTF8 for all imports?
THe question is
acters properly. I
> attached the file for your play-around.
>
> When I import the file on the command line with the UTF8 option tex2lyx
> -e UTF8 ch1.tex, the LyX file looks just fine except one or two characters.
>
> So is there a way to tell to tex2lyx to use UTF8 encoding from withi
and line with the UTF8 option tex2lyx
-e UTF8 ch1.tex, the LyX file looks just fine except one or two characters.
So is there a way to tell to tex2lyx to use UTF8 encoding from within
LyX? This issue is occured when I import a tex file that has
\input{ch1.tex} in it. So, maybe LyX has and option
Am Donnerstag, den 07.06.2018, 13:40 +0200 schrieb Kornel Benko:
> tex2lyx still (again?) has some quirks.
> Importing development/batchtests/ams-import.tex leads to correct
> display in lyx, but
> the tex-file used to compile with e.g. pdflatex is wrong.
>
> The origin
Am Donnerstag, 24. Mai 2018 20:55:12 CEST schrieb Kornel Benko :
>
> New test: AMS-import.
>
tex2lyx still (again?) has some quirks.
Importing development/batchtests/ams-import.tex leads to correct display in
lyx, but
the tex-file used to compile with e.g. pdflatex is wrong.
The
Am Donnerstag, 24. Mai 2018 12:18:24 CEST schrieb Jürgen Spitzmüller
:
> 2018-05-24 12:10 GMT+02:00 Kornel Benko :
>
> > Why no commit?
> >
>
> I just wanted to hear whether there are objections or comments. This part
> of the code is not my homeland.
>
>
> > I could prepare a testcase in deve
2018-05-24 12:10 GMT+02:00 Kornel Benko :
> Why no commit?
>
I just wanted to hear whether there are objections or comments. This part
of the code is not my homeland.
> I could prepare a testcase in development/batchtests.
>
> Something like
>
> buffer-new
>
> buffer-import pdflatex theorem-ams
Am Donnerstag, 24. Mai 2018 10:24:34 CEST schrieb Jürgen Spitzmüller
:
> 2018-05-22 9:12 GMT+02:00 Jürgen Spitzmüller :
>
> > It's the [section]. See attached file. This looks like a bug. Could you
> > file a report, please?
> >
>
> Ticket and patch here:
> https://www.lyx.org/trac/ticket/11156
2018-05-22 9:12 GMT+02:00 Jürgen Spitzmüller :
> It's the [section]. See attached file. This looks like a bug. Could you
> file a report, please?
>
Ticket and patch here:
https://www.lyx.org/trac/ticket/11156
Jürgen
2018-05-22 9:12 GMT+02:00 Jürgen Spitzmüller
> It's the [section]. See attached file. This looks like a bug. Could you
> file a report, please?
>
The problem is that checkModule() (in tex2lyx.cpp) does not check for
module requirements. It does read the module that provides a specific
layout, but
icated of an issue. I also recommend that when
collaborating, you should use the same set of tools. Although LyX
exports LaTeX, it is not a LaTeX editor.
As Riki mentioned, there are continued improvements. see the "tex2lyx"
section of the following for recent improvements that will b
> greatest obstacle to wider use is that Tex2LyX does not work reliably. By the
> nature of the task, Tex2LyX is trying to convert files that were not written
> for LyX, so requiring special forms of LaTex devalues the program. When I
> collaborate I end up using LaTex instead of LyX
rrectly? For instance most files I receive from collaborators do not have the
theorem definitions in the right form.
I think LyX is a great tool, both for learning LaTex and doing serious writing.
However none of my 70 coauthors have used it, and except for my current
students, I know of nobody in my
2018-05-22 9:17 GMT+02:00 Jean-Marc Lasgouttes:
> > \begin{thm}
> > For every $\epsilon>0$, there is a constant $\delta>0$ so that if
> > \end{theorem}
>
Yes, thanks. Fixing that does not help, though.
Jürgen
Le 22/05/2018 à 09:12, Jürgen Spitzmüller a écrit :
Am Dienstag, den 22.05.2018, 09:04 +0200 schrieb Jürgen Spitzmüller:
One problem is that the theorems are named and defined differently to
those LyX supports ("theorem" and "corollary" vs. "thm" and "cor"),
and
see
https://www.lyx.org/trac/tic
Am Dienstag, den 22.05.2018, 09:04 +0200 schrieb Jürgen Spitzmüller:
> One problem is that the theorems are named and defined differently to
> those LyX supports ("theorem" and "corollary" vs. "thm" and "cor"),
> and
> see
>
> https://www.lyx.org/trac/ticket/10432
>
> If I change that, it sill do
Am Montag, den 21.05.2018, 11:24 -0400 schrieb Richard Kimberly Heck:
> On 05/19/2018 06:55 PM, Hal Kierstead wrote:
> > All -
> >
> > I am using LyX 2.3.0 on macOS 10.13.4. When I try to import a tex
> > file I get ert for every theorem type statement. Is there away to
> > avoid this?
>
> Someon
On 05/19/2018 06:55 PM, Hal Kierstead wrote:
> All -
>
> I am using LyX 2.3.0 on macOS 10.13.4. When I try to import a tex file I get
> ert for every theorem type statement. Is there away to avoid this?
Someone else should be able to answer this better, but I believe this is
supposed to work.
Ri
All -
I am using LyX 2.3.0 on macOS 10.13.4. When I try to import a tex file I get
ert for every theorem type statement. Is there away to avoid this? I know I can
go through by hand and correct each occurrence, but it would be much better if
the converter handled it. At least it compiles.
Here
On 2017-09-25, Paul A. Rubin wrote:
> On 09/25/2017 10:35 AM, Patrick Dupre wrote:
>> No, It do not have the layout!
> Well, there's your problem. No layout, no using the class with LyX. If
> you can find an osajnl.layout file somewhere online, deposit it in your
> local layouts folder, reconfig
On 09/25/2017 10:35 AM, Patrick Dupre wrote:
No, It do not have the layout!
Well, there's your problem. No layout, no using the class with LyX. If
you can find an osajnl.layout file somewhere online, deposit it in your
local layouts folder, reconfigure and restart LyX, and you should be
able
uot;
> To: "Patrick Dupre" , lyx
> Subject: Re: tex2lyx
>
> On 09/25/2017 10:22 AM, Patrick Dupre wrote:
> > Hello,
> >
> > Apparently this tex template is acceptable for the OSA.
> > However, it fails when I try to convert it to lyx.
> > Cannot
On 09/25/2017 10:22 AM, Patrick Dupre wrote:
Hello,
Apparently this tex template is acceptable for the OSA.
However, it fails when I try to convert it to lyx.
Cannot read layout file `'.
Error reading `'
(Check `osajnl')
Check your installation and try Options/Reconfigure...
Error: Could not rea
Hello,
Apparently this tex template is acceptable for the OSA.
However, it fails when I try to convert it to lyx.
Cannot read layout file `'.
Error reading `'
(Check `osajnl')
Check your installation and try Options/Reconfigure...
Error: Could not read layout file for textclass "osajnl".
\docume
On 11/17/2016 05:36 PM, Jay A. Leavitt, PhD wrote:
> Running Win 10, LyX 2.2.2
> template.tex is a template for Springer publications. Latex files with
> Springer macros cannot import into LyX.
> LyX: Cannot convert file. An error occurred while running:
> tex2lyx -fixedenc utf8 -
Running Win 10, LyX 2.2.2
template.tex is a template for Springer publications. Latex files with
Springer macros cannot import into LyX.
LyX: Cannot convert file. An error occurred while running:
tex2lyx -fixedenc utf8 -f "template.tex" "template.lyx"
---
This email
On 09/05/2014 03:18 AM, Mark A Pinsky wrote:
I'm running Lyx 2.1 and trying to convert tex-file to lyx-file.
Follow the standard pass: file> import>Latex(plain); however am
getting an error message:
An error occurred while running tex2lyx-f"root1.tex""root1.lyx
I'm running Lyx 2.1 and trying to convert tex-file to lyx-file. Follow the
standard pass: file> import>Latex(plain); however am getting an error message:
An error occurred while running tex2lyx-f"root1.tex""root1.lyx"
What should I do?
Thanks,
Mark
On 04/01/2014 10:42 PM, Okhaide Akhigbe
wrote:
I am trying to import the springer "BioMed
Central's TeX template" (http://www.springeropen.com/authors/tex),
for use in a journal.
When I import I
I am trying to import the springer "BioMed Central's TeX template" (
http://www.springeropen.com/authors/tex), for use in a journal.
When I import I get this error
[image: Inline image 1]
The following is my configurations:
Windows 8 64bit
LyX 2.0.7
MikeTex 2.9
<>
or "An error occured while running: tex2lyx..."
First question is: What LaTeX class is this, and is there an equivalent LyX
layout file? See
http://wiki.lyx.org/FAQ/SurprisesForNewUsers#new-class
HTH
Jürgen
Hello,
I am a student hoping to use LyX to format my thesis. My university
provides a template .tex file which I am not required to use, but would
save me some time. When I try to import the file into LyX, I recieve the
error "An error occured while running: tex2lyx..." Based upon m
Le 26/01/14 21:07, Ingar Pareliussen a écrit :
I thought that tex2lyx translated these macros away from macros to
char-encodings, and thus is should be, in these cases, safe to remove
the braces as part of the conversion.
You are right of course, I was trying this argument in order to avoid
thing here. :)
I thought that tex2lyx translated these macros away from macros to
char-encodings, and thus is should be, in these cases, safe to remove
the braces as part of the conversion.
However, one could argue that the writer2latex is doing it wrong as you
probably should write \ae{}
Le 26/01/14 19:09, Ingar Pareliussen a écrit :
When importing Norwegian texts latex encoded special character get translated.{\aa}
-> {å} and [\o} -> {ø} etc. However, the { and } are imported as ERT and makes
the text very hard to read.
Could tex2lyx removed the extra {} when importin
When importing norwegian texts latex encoded special charcter get
translated.{\aa} -> {å} and [\o} -> {ø} etc. However, the { and } are imported
as ERT and makes the text very hard to read.
Could tex2lyx removed the extra {} when importing?
Ingar
read layout file for textclass "acmtog".
>
It seems that tex2lyx expects a layout file to be present, but TOG class do
not define one.
Any advices for fixing this problem?
Matti L
--
Life is complex. It has real and imaginary parts.
All,
Thanks, I will try ubuntu version then.
Greeting,
Hayu
On Mon, 15 Jul 2013 11:23:33 + (UTC)
Hayuning wrote:
> Hello,
>
> In the announcement of the latest version, Lyx 2.0.6, it is said that
> they add new option -m to select needed modules (bug 8393).
>
> We know that one of the Lyx issues is that if we import Tex file to
> Lyx, it does not re
On Mon, Jul 15, 2013 at 7:23 AM, Hayuning wrote:
> Hello,
>
> In the announcement of the latest version, Lyx 2.0.6, it is said that they add
> new option -m to select needed modules (bug 8393).
>
> We know that one of the Lyx issues is that if we import Tex file to Lyx, it
> does not recognize the
Hello,
In the announcement of the latest version, Lyx 2.0.6, it is said that they add
new option -m to select needed modules (bug 8393).
We know that one of the Lyx issues is that if we import Tex file to Lyx, it
does not recognize the theorem module, instead it will appear as ERT.
With that n
On 05/03/2012 12:12 PM, Barger, Carla wrote:
Hi,
Lyx 2.0.3
MS Windows 7 (Ultimate)
I'm trying to import into lyx from tex. The dialog box says that the tex2lyx
command failed but did not say anything further. As it happens, it failed
because python was not installed. It would be ni
On 03/05/2012 12:23 PM, Barger, Carla wrote:
What can be done so that tex import works from the file menu?
Since you installed python after you installed LyX, you should
reconfigure LyX (from the Tools menu).
--
David L. Johnson
Arguing with an engineer is like mud wrestling with a pig.
On 2012-02-19, Georg Baum wrote:
> Guenter Milde wrote:
>> On 2012-02-15, Georg Baum wrote:
>>> Jean-Marc Lasgouttes wrote:
>>> Unfortunately I know next to nothing about use_non_tex_fonts. After
>>> reading the code and user guide a bit I see that using xetex is only
>>> possible if use_non_tex_f
On Feb 19, 2012, at 1:36 PM, stefano franchi wrote:
> I am forwarding to the users' list. This problem starts to exceed my
> lyx/Latex skills. What I can say is this:
>
> If I:
>
> 1. Import your file with the modified latex converter
>
> 2. Change fonts to non-latex
>
> 3. Select full-cov
On Sun, Feb 19, 2012 at 11:00 AM, Eric Weir wrote:
>
> On Feb 19, 2012, at 9:54 AM, stefano franchi wrote:
>
> On Sun, Feb 19, 2012 at 5:13 AM, Eric Weir wrote:
>
>
> On Feb 18, 2012, at 8:16 AM, Eric Weir wrote:
>
>
> After both types of imports I get the following message: "Could not find
>
> L
Guenter Milde wrote:
> On 2012-02-15, Georg Baum wrote:
>> Jean-Marc Lasgouttes wrote:
>
>>> Georg, Juergen, I'd like some feedback on the soundness of the patch. I
>>> know next to nil about xetex, and I do not know what is the current
>>> state o
On Feb 18, 2012, at 8:16 AM, Eric Weir wrote:
> After both types of imports I get the following message: "Could not find
> LaTeX command for character''(code point 0x2028)
> Some characters of your document are probably not representable in the chosen
> encoding. Changing the document encoding
On Feb 17, 2012, at 9:36 AM, Eric Weir wrote:
> On Feb 16, 2012, at 7:47 PM, stefano franchi wrote:
>
>> try this workaround to the workaround. Instead of creating a new
>> converter, simply go to the existing LAtex(plain-->lyx converter, look
>> at the command st
On Feb 16, 2012, at 10:45 AM, stefano franchi wrote:
> On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir wrote:
>>
>> On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
>>
>>> On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir wrote:
>>>
Thanks, Stefano. Don't see how to do that, either. Scrivener do
On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir wrote:
>
> On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
>
>> On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir wrote:
>>
>>> Thanks, Stefano. Don't see how to do that, either. Scrivener does not
>>> appear on the dropdown list. Perhaps there is somethin
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
> On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir wrote:
>
>> Thanks, Stefano. Don't see how to do that, either. Scrivener does not appear
>> on the dropdown list. Perhaps there is something on the list that would
>> stand in for the Scrivener ou
om
>>>> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and
>>>> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch
>>>> in the "Converter field":
>>>> tex2lyx -e UTF8 -f $$i $$o
>
Eric Weir wrote:
> > (IMV, the name for this setting should also be changed:
> > - use_non_tex_fonts
> > + use_fontspec
> >
> > this would prevent much confusion.)
>
> While I now know what it refers to, as a new user I would otherwise have
> found the new description mystifying. I would seem th
pdown list, and
>>> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch
>>> in the "Converter field":
>>> tex2lyx -e UTF8 -f $$i $$o
>
>
>
> And, you need to create the new format before you can create the con
On Feb 16, 2012, at 4:35 AM, Guenter Milde wrote:
> (IMV, the name for this setting should also be changed:
> - use_non_tex_fonts
> + use_fontspec
> this would prevent much confusion.)
While I now know what it refers to, as a new user I would otherwise have found
the new description mystifyin
On 2012-02-15, Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
>> Georg, Juergen, I'd like some feedback on the soundness of the patch. I
>> know next to nil about xetex, and I do not know what is the current
>> state of the art wrt tex2lyx.
> Unfortunately
c" package
(coupled with the use of polyglossia if the language-package
setting is set to auto, if I remember right).
The "fontspec" package can be used with the XeTeX and LuaTeX engines but not
with TeX and eTeX.
This means that tex2lyx should look for
\usepackage{fontspec}
and se
Jürgen Spitzmüller wrote:
> LuaTeX can use other encodings, but not with non-tex fonts. So if
> \use_non_tex_fonts is true (this is what you want to check for, right?),
> the encoding of the file must be utf8.
No, it is the other way round: If a xetex package is detected,
use_non_tex_fonts is se
Jean-Marc Lasgouttes wrote:
> Georg, Juergen, I'd like some feedback on the soundness of the patch. I
> know next to nil about xetex, and I do not know what is the current
> state of the art wrt tex2lyx.
Unfortunately I know next to nothing about use_non_tex_fonts. After reading
nd
>> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch
>> in the "Converter field":
>> tex2lyx -e UTF8 -f $$i $$o
>
> In Tools I do not have the Preferences option. If I go to Preferences > File
> Handling > Converters
>> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch
>> in the "Converter field":
>> tex2lyx -e UTF8 -f $$i $$o
>
> In Tools I do not have the Preferences option. If I go to Preferences > File
> Handling > Converters t
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
> 3. In Tools>>Preferences>>FIle Converters, create a new converter from
> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and
> "Lyx" in the "to list. Enter the call to tex2lyx
.
This might be a LyX limitation. However this is about tex2lyx, so we would
check for \usepackage{fontenc} or \usepackage{xunicode}.
I propose to also check for
> \usepackage[]{luainputenc}
Günter
om
> Scrivener to Lyx: select "Scrivener" in the From dropdown list, and
> "Lyx" in the "to list. Enter the call to tex2lyx with the UTF8 switch
> in the "Converter field":
> tex2lyx -e UTF8 -f $$i $$o
>
> 4. Click "Add" and click &quo
he workaround involves use
>>> of the tex2lyx command.
>>>
>>> I'm on a Mac. When I run the command I get a command not found message.
>>> When I do locate tex2lyx, however, the file shows up in two locations:
>>> /Applications/LyX.app/Contents/Mac
On Feb 14, 2012, at 4:47 PM, Enrico Forestieri wrote:
> Eric Weir writes:
>> I'm attempting to use the workaround suggested by Stefano to get LyX to
>> recognize a Unicoded document as Unicoded. The workaround involves use
>> of the tex2lyx command.
>>
>>
Jean-Marc Lasgouttes wrote:
> I thought LuaTeX could use encdings other than utf8. Is utf8 the
> default? And does it use the same packages as XeTeX?
LuaTeX can use other encodings, but not with non-tex fonts. So if
\use_non_tex_fonts is true (this is what you want to check for, right?), the
en
Le 15/02/2012 11:38, Jürgen Spitzmüller a écrit :
Jean-Marc Lasgouttes wrote:
> I have a patch that seems to work with XeTeX, I do not know anything
> about luatex (what shall we do with it?)
I think your patch will work for LuaTeX as well.
I thought LuaTeX could use encdings other than ut
Jean-Marc Lasgouttes wrote:
> I have a patch that seems to work with XeTeX, I do not know anything
> about luatex (what shall we do with it?)
I think your patch will work for LuaTeX as well.
Jürgen
Le 15/02/2012 10:51, Guenter Milde a écrit :
IMV, it should try utf8 first in case this does not give a result.
* if the file is pure ASCII, everything is fine
* if the file is utf8 encoded, fine too
* if another encoding is used, an error occures: try again with the second
guess.
That is n
On 2012-02-14, stefano franchi wrote:
> On Tue, Feb 14, 2012 at 8:05 AM, Jean-Marc Lasgouttes
>> tex2lyx is not really the culprit. The file you attach is broken : it
>> does not use xetex/luatex, but it does use "Unicode (XeTeX) (utf8)" as
>> encoding. As a resul
Eric Weir writes:
> I'm attempting to use the workaround suggested by Stefano to get LyX to
> recognize a Unicoded document as Unicoded. The workaround involves use
> of the tex2lyx command.
>
> I'm on a Mac. When I run the command I get a command not found message.
&
On Tue, Feb 14, 2012 at 11:18 AM, Eric Weir wrote:
>
> On Feb 14, 2012, at 11:07 AM, BH wrote:
>
>> I'm guessing the problem is that tex2lyx isn't in your PATH, which
>> means you must provide it yourself. So from the Terminal, you should
>> type, for example,
) produces garbage characters for the dashes
>>>
>>> 2. However, calling>tex2lyx -e UTF8 from the command line produces
>>> the correct file.
>>
>> Still, it's surprising we fail in this particular case, so I'd guess it
>> is indeed a bug. I&#x
On Feb 14, 2012, at 11:07 AM, BH wrote:
> I'm guessing the problem is that tex2lyx isn't in your PATH, which
> means you must provide it yourself. So from the Terminal, you should
> type, for example,
>
> /Applications/LyX.app/Contents/MacOS/tex2lyx
Thanks, Will do
> recognize a Unicoded document as Unicoded. The workaround involves use of
> the tex2lyx command.
>
> I'm on a Mac. When I run the command I get a command not found message. When
> I do locate tex2lyx, however, the file shows up in two
> locations: /Applications/LyX.app/
f the
tex2lyx command.
I'm on a Mac. When I run the command I get a command not found message. When I
do locate tex2lyx, however, the file shows up in two locations:
/Applications/LyX.app/Contents/MacOS and
/Applications/TeX/LyX.app/Contents/MacOS
How do I get the command to ru
I'm attempting to use the workaround suggested by Stefano to get LyX to
recognize a Unicoded document as Unicoded. The workaround involves use of the
tex2lyx command.
I'm on a Mac. When I run the command I get a command not found message. When I
do locate tex2lyx, however, the f
Jean-Marc Lasgouttes wrote:
> Georg, Juergen, I'd like some feedback on the soundness of the patch. I
> know next to nil about xetex, and I do not know what is the current
> state of the art wrt tex2lyx.
The latter I don't know either, but the patch looks sane. We set th
Le 14/02/2012 00:47, Richard Heck a écrit :
Try out the enclosed minimal lyx file.
1. exporting to latex and reimporting into lyx from
FIle>>Import>>Latex(plain) produces garbage characters for the dashes
2. However, calling>tex2lyx -e UTF8 from the command line produces
t
efforts on behalf of the LyX community.
So tex2lyx is the culprit. Wasn't this solved some time ago, however?I
mean: automatic recognition of the imported file encoding?
Well, that's a complicated issue. They may have tried to do a better
job, but recognizing the file encoding complete
I have been helping Eric Weir with his Scrivener-->LaTeX-->Lyx import
and we have narrowed down the problem to Lyx not importing a
Unicode-encoded file as Unicode.
So tex2lyx is the culprit. Wasn't this solved some time ago, however?I
mean: automatic recognition of the imported file enc
Hi,
can someone remember me how to use tex2lyx with custom macros, so that
they're imported as a single inset, and not the separated macro name,
the open brace and closed braces ?
Thx,
T.
1 - 100 of 244 matches
Mail list logo
