;> 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?
>>>>
>>>> I found exactly same question on this post, but the answers
ut{ch1.tex} in it. So, maybe LyX has and option to force tex2lyx to
> >> read in UTF8 for all imports?
> >>
> >> I found exactly same question on this post, but the answers seem to be
> >> unrelated:
> >>
> >> https://lyx-users.lyx.narkive.c
found exactly same question on this post, but the answers seem to be
>> unrelated:
>>
>> https://lyx-users.lyx.narkive.com/Rg1StNIT/how-to-force-tex2lyx-to-read-unicode-from-within-lyx
>>
>> Thanks
>>
>> Baris
>>
>
> Found the answer:
Well, that's *an*
in it. So, maybe LyX has and option to force tex2lyx to
read in UTF8 for all imports?
I found exactly same question on this post, but the answers seem to be
unrelated:
https://lyx-users.lyx.narkive.com/Rg1StNIT/how-to-force-tex2lyx-to-read-unicode-from-within-lyx
Thanks
Baris
Found the ans
Well, seems like file->import simply calls tex2lyx.exe without any
option such as "-e UTF8". It should not be very difficult to let the
user enter his choice of options...
On 11/2/2018 10:43 PM, Jean-Marc Lasgouttes wrote:
> Le 02/11/2018 à 10:33, Baris Erkus a écrit :
>> So is there a way to t
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 w
//lyx-users.lyx.narkive.com/Rg1StNIT/how-to-force-tex2lyx-to-read-unicode-from-within-lyx
>
> Thanks
>
> Baris
>
I can reproduce the incorrect LaTeX import, and also Vim says the file
encoding is "utf-8". I can also reproduce with LyX 2.1.0, so it appears
it i
to force tex2lyx to
read in UTF8 for all imports?
I found exactly same question on this post, but the answers seem to be
unrelated:
https://lyx-users.lyx.narkive.com/Rg1StNIT/how-to-force-tex2lyx-to-read-unicode-from-within-lyx
Thanks
Ba
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
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
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
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 I know next to nothing about use_non_te
On 2012-02-15, Georg Baum wrote:
> Jürgen Spitzmüller wrote:
>> If other encodings are used, LuaTeX uses the "luainputenc" package, which
>> has the same syntax than inputenc, i.e.
>> \usepackage[]{luainputenc}
>> Maybe we have to care about that.
> luainputenc is already handled.
Fine.
> Wha
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
the code and use
On 2012-02-15, Jürgen Spitzmüller wrote:
> 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.
Are you sure. I'd think that with "lua
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 result, the latex export of the file do
On Tue, Feb 14, 2012 at 8:05 AM, Jean-Marc Lasgouttes
wrote:
> 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. H
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 inter
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
the correct file.
Stil
On 02/13/2012 05:41 PM, stefano franchi wrote:
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.
I'm glad to hear someone was able to help with this. Thanks for your
efforts on beha
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 encoding?
Try
27 matches
Mail list logo
