Re: Problem using tex2lyx Unicode char \u8:�in not set up for use with LaTeX.
On 2010-05-27, Jean-Marc Lasgouttes wrote: b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up for use w= ith LaTeX. The standard unicode input encoding (utf8) is rather limited. LyX has a more comprehensive translation table, so setting the output encoding to language default (in DocumentSettingsLanguage) might solve this problem. However the question is to know why the encoding is set to utf8 by tex2lyx. Most probably because the original file used it. However, in this case the question is, how the non-translable Unicode character came into the file: * Does tex2lyx do reverse engineering of LaTeX commands to unicode characters? * or, maybe the OP did insert it after the conversion to LyX? A minimal example file would help. Günter
Re: Problem using tex2lyx "Unicode char \u8:�in not set up for use with LaTeX."
On 2010-05-27, Jean-Marc Lasgouttes wrote: >>> b) When converting to PDF via pdflatex I ran into several problems: >>> b1) (a lot of them) wrong input encoding: >>> ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up >>> for use w= >>> ith LaTeX. >> The standard unicode input encoding (utf8) is rather limited. LyX >> has a >> more comprehensive translation table, so setting the output encoding >> to >> "language default" (in Document>Settings>Language) might solve this >> problem. > However the question is to know why the encoding is set to utf8 by > tex2lyx. Most probably because the original file used it. However, in this case the question is, how the non-translable Unicode character came into the file: * Does tex2lyx do "reverse engineering" of LaTeX commands to unicode characters? * or, maybe the OP did insert it after the conversion to LyX? A minimal example file would help. Günter
Re: Problem using tex2lyx Unicode char \u8: �in not set up for use with LaTeX.
b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up for use w= ith LaTeX. The standard unicode input encoding (utf8) is rather limited. LyX has a more comprehensive translation table, so setting the output encoding to language default (in DocumentSettingsLanguage) might solve this problem. However the question is to know why the encoding is set to utf8 by tex2lyx. JMarc
Re: Problem using tex2lyx "Unicode char \u8: �in not set up for use with LaTeX."
b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up for use w= ith LaTeX. The standard unicode input encoding (utf8) is rather limited. LyX has a more comprehensive translation table, so setting the output encoding to "language default" (in Document>Settings>Language) might solve this problem. However the question is to know why the encoding is set to utf8 by tex2lyx. JMarc
Re: Problem using tex2lyx Unicode char \u8:�in not set up for use with LaTeX.
On 2010-05-22, Niklaus Giger wrote: ... But when I tried to import all the files from https://elexis.svn.sourceforge.net/svnroot/elexis/trunk/doc_fr I did run into several problems: ... b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up for use w= ith LaTeX. The standard unicode input encoding (utf8) is rather limited. LyX has a more comprehensive translation table, so setting the output encoding to language default (in DocumentSettingsLanguage) might solve this problem. Günter
Re: Problem using tex2lyx "Unicode char \u8:�in not set up for use with LaTeX."
On 2010-05-22, Niklaus Giger wrote: ... > But when I tried to import all the files from > https://elexis.svn.sourceforge.net/svnroot/elexis/trunk/doc_fr > I did run into several problems: ... > b) When converting to PDF via pdflatex I ran into several problems: > b1) (a lot of them) wrong input encoding: > ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up for use w= > ith LaTeX. The standard unicode input encoding (utf8) is rather limited. LyX has a more comprehensive translation table, so setting the output encoding to "language default" (in Document>Settings>Language) might solve this problem. Günter
Re: Problem using tex2lyx Unicode char \u8: �in not set up for use with LaTeX.
Niklaus Giger niklaus.gi...@member.fsf.org writes: b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:�in not set up for use with LaTeX. This error seems to occur only on section headings. b2) (few) ! Package inputenc Error: Keyboard character is undefined b3) (few) Hello, What would be very nice is to have a small-ish tex file that exhibits this problem. Could you make one for us? JMarc
Re: Problem using tex2lyx "Unicode char \u8: �in not set up for use with LaTeX."
Niklaus Gigerwrites: > b) When converting to PDF via pdflatex I ran into several problems: > b1) (a lot of them) wrong input encoding: > ! Package inputenc Error: Unicode char \u8:�in not set up for use with LaTeX. > > This error seems to occur only on section headings. > > b2) (few) > ! Package inputenc Error: Keyboard character is undefined > b3) (few) Hello, What would be very nice is to have a small-ish tex file that exhibits this problem. Could you make one for us? JMarc
Problem using tex2lyx Unicode char \u8:�in not set up for use with LaTeX.
Hi For many years LyX has been (almost exclusively) my only private document editor and I was always very pleased with it. Thanks a lot for your hard work. We are a small team who would like to translate the (free) Eclipse RCP application Elexis (www.elexis.ch) for medical practitioner to French. Our medical doctor Bruno Büchel invested a lot of time, but after many years using Word he had a hard time to work with the LaTeX files using WinEdit. Therefore I proposed using LyX and said that there should be no problem importing the existing *.tex files into LyX. And importing just a few chapters (e.g. konzepte.tex) worked quite well. I added to the LaTeX Vorspann \usepackage{wrapfig}%\usepackage{placeins} But when I tried to import all the files from https://elexis.svn.sourceforge.net/svnroot/elexis/trunk/doc_fr I did run into several problems: a) I had to write to small Ruby-script. a1) to correct some paths for the imported images and adding *.png to the filenames where they were missing (see attachment) a2) correct imported *.tex - *.lyx a3) (not yet implemented) add usepackage{wrapfig} where needed b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:�in not set up for use with LaTeX. This error seems to occur only on section headings. b2) (few) ! Package inputenc Error: Keyboard character is undefined b3) (few) I would appreciate if somebody could have a look at why I have so many input encoding errors. The other ones I will probably just be some manual work and tweaking of my Ruby script. I am running LyX 1.6.5 on my Debian/GNU/LInux System (squeeze). Tried to compile 1.6.6 and 2.0.x but got (more or less) the same errors. Didn't find a tex2lyx bug on the bug tracker. Best regards Niklaus P.S: Please cc to me as I am not subscribed to the LyX mailing list. ng2lyx.rb Description: application/ruby
Problem using tex2lyx "Unicode char \u8:�in not set up for use with LaTeX."
Hi For many years LyX has been (almost exclusively) my only private document editor and I was always very pleased with it. Thanks a lot for your hard work. We are a small team who would like to translate the (free) Eclipse RCP application "Elexis" (www.elexis.ch) for medical practitioner to French. Our medical doctor Bruno Büchel invested a lot of time, but after many years using Word he had a hard time to work with the LaTeX files using WinEdit. Therefore I proposed using LyX and said that there should be no problem importing the existing *.tex files into LyX. And importing just a few chapters (e.g. konzepte.tex) worked quite well. I added to the LaTeX Vorspann "\usepackage{wrapfig}%\usepackage{placeins}" But when I tried to import all the files from https://elexis.svn.sourceforge.net/svnroot/elexis/trunk/doc_fr I did run into several problems: a) I had to write to small Ruby-script. a1) to correct some paths for the imported images and adding *.png to the filenames where they were missing (see attachment) a2) correct imported *.tex -> *.lyx a3) (not yet implemented) add usepackage{wrapfig} where needed b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:�in not set up for use with LaTeX. This error seems to occur only on section headings. b2) (few) ! Package inputenc Error: Keyboard character is undefined b3) (few) I would appreciate if somebody could have a look at why I have so many input encoding errors. The other ones I will probably just be some manual work and tweaking of my Ruby script. I am running LyX 1.6.5 on my Debian/GNU/LInux System (squeeze). Tried to compile 1.6.6 and 2.0.x but got (more or less) the same errors. Didn't find a tex2lyx bug on the bug tracker. Best regards Niklaus P.S: Please cc to me as I am not subscribed to the LyX mailing list. ng2lyx.rb Description: application/ruby