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 to
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 of the art wrt tex2lyx.
Unfortunately I know next
On Sun, Feb 19, 2012 at 11:00 AM, Eric Weir eew...@bellsouth.net wrote:
On Feb 19, 2012, at 9:54 AM, stefano franchi wrote:
On Sun, Feb 19, 2012 at 5:13 AM, Eric Weir eew...@bellsouth.net wrote:
On Feb 18, 2012, at 8:16 AM, Eric Weir wrote:
After both types of imports I get the following
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-coverage
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
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 of the
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
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
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 string (the tex2lyx etc.) and stick a -e
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 string (the tex2lyx etc.) and stick a -e
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 comm
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 set use_non_tex_fonts accordingly.
(IMV, the name for this setting should also be changed
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 I know next to nothing about use_non_tex_fonts
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 mystifying.
On Feb 15, 2012, at 1:57 PM, stefano franchi wrote:
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
3. In ToolsPreferencesFIle 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
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 that it's
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
And, you need to create the new format before you can create the converter.
Thanks, Stefano. Don't see how to do that, either. Scrivener does
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir eew...@bellsouth.net 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
On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir eew...@bellsouth.net wrote:
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir eew...@bellsouth.net wrote:
Thanks, Stefano. Don't see how to do that, either. Scrivener does not
appear on the dropdown
On Feb 16, 2012, at 10:45 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir eew...@bellsouth.net wrote:
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir eew...@bellsouth.net wrote:
Thanks, Stefano. Don't see how to do
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 set use_non_tex_fonts accordingly.
(IMV, the name for this setting should also be changed
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 I know next to nothing about use_non_tex_fonts
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 mystifying.
On Feb 15, 2012, at 1:57 PM, stefano franchi wrote:
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
3. In ToolsPreferencesFIle 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
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 that it's
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
And, you need to create the new format before you can create the converter.
Thanks, Stefano. Don't see how to do that, either. Scrivener does
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir eew...@bellsouth.net 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
On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir eew...@bellsouth.net wrote:
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir eew...@bellsouth.net wrote:
Thanks, Stefano. Don't see how to do that, either. Scrivener does not
appear on the dropdown
On Feb 16, 2012, at 10:45 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 9:40 AM, Eric Weir eew...@bellsouth.net wrote:
On Feb 16, 2012, at 9:37 AM, stefano franchi wrote:
On Thu, Feb 16, 2012 at 6:35 AM, Eric Weir eew...@bellsouth.net wrote:
Thanks, Stefano. Don't see how to do
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
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 I kn
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
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
>
>
>
> And, you need to create the new format before you can create the con
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
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 with the UTF8 switch
>>>> in the "Converter field":
>>>>
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
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
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.
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 result, the latex export of the file does
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
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 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
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
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.
I'm on a Mac. When I run the command I get
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/MacOS and
/Applications/TeX/LyX.app/Contents/MacOS
How do I get the command to run?
Why don't
the call to tex2lyx with the UTF8 switch
in the Converter field:
tex2lyx -e UTF8 -f $$i $$o
4. Click Add and click Save.
Now you should have the Scrivener (or whatever you called the
format) option in FileImport, without needing to go to the command
line. In fact Lyx does internally
this is about tex2lyx, so we would
check for \usepackage{fontenc} or \usepackage{xunicode}.
I propose to also check for
\usepackage[enc]{luainputenc}
Günter
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
3. In ToolsPreferencesFIle 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 with the UTF8 switch
in the Converter field:
tex2lyx -e
Am 15.02.2012 um 17:59 schrieb Eric Weir:
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
3. In ToolsPreferencesFIle 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 with the UTF8
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 the add button is greyed out. I don't see how to add
a new converter.
Sorry, that was Linux--As Stephan
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
the code and user
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 set
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 result, the latex export of the file does
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
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 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
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
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.
I'm on a Mac. When I run the command I get
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/MacOS and
/Applications/TeX/LyX.app/Contents/MacOS
How do I get the command to run?
Why don't
the call to tex2lyx with the UTF8 switch
in the Converter field:
tex2lyx -e UTF8 -f $$i $$o
4. Click Add and click Save.
Now you should have the Scrivener (or whatever you called the
format) option in FileImport, without needing to go to the command
line. In fact Lyx does internally
this is about tex2lyx, so we would
check for \usepackage{fontenc} or \usepackage{xunicode}.
I propose to also check for
\usepackage[enc]{luainputenc}
Günter
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
3. In ToolsPreferencesFIle 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 with the UTF8 switch
in the Converter field:
tex2lyx -e
Am 15.02.2012 um 17:59 schrieb Eric Weir:
On Feb 15, 2012, at 10:55 AM, stefano franchi wrote:
3. In ToolsPreferencesFIle 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 with the UTF8
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 the add button is greyed out. I don't see how to add
a new converter.
Sorry, that was Linux--As Stephan
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
the code and user
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 set
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
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
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 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
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
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.
>>
>> I'm
ed 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.a
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 &q
is 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
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
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 > Conve
ener" 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
>
> In Tools I do not have the Preferences option. If I go to Preferences > File
>
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
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
, it's surprising we fail in this particular case, so I'd guess it
is indeed a bug. I'll cross-post to devel.
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 result, the latex export
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 the encoding
to utf8
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 file shows
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/MacOS and
/Applications/TeX/LyX.app/Contents/MacOS
How do I get the command to run?
Thanks
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/Contents/MacOS
and /Applications/TeX
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. But while I'm
. However, callingtex2lyx -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'll cross-post to devel.
tex2lyx is not really the culprit. The file you attach is broken : it does
not use xetex/luatex
On Tue, Feb 14, 2012 at 11:18 AM, Eric Weir eew...@bellsouth.net 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,
/Applications/LyX.app
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.
When I do locate tex2lyx
, it's surprising we fail in this particular case, so I'd guess it
is indeed a bug. I'll cross-post to devel.
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 result, the latex export
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 the encoding
to utf8
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 file shows
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/MacOS and
/Applications/TeX/LyX.app/Contents/MacOS
How do I get the command to run?
Thanks
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/Contents/MacOS
and /Applications/TeX
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. But while I'm
. However, callingtex2lyx -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'll cross-post to devel.
tex2lyx is not really the culprit. The file you attach is broken : it does
not use xetex/luatex
On Tue, Feb 14, 2012 at 11:18 AM, Eric Weir eew...@bellsouth.net 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,
/Applications/LyX.app
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.
When I do locate tex2lyx
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
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 the encoding
101 - 200 of 633 matches
Mail list logo