[opensuse] Can't produce any usable output with LyX
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
On Sunday 03 February 2008 07:31:03 am Carlos E. R. wrote:
I search for CJK.sty, and found it in package texlive-cjk-2007-69.noarch.rpm which I install, even though I don't understand why I have to install CJK support to write in Spanish:
Me neither. I mean why you install CJK support for Spanish ;-) I never asked myself what is necessary for browsing and what for writing. Maybe some of experts for printing can help us. -- Regards, Rajko. See http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-03 at 08:24 -0600, Rajko M. wrote:
On Sunday 03 February 2008 07:31:03 am Carlos E. R. wrote:
I search for CJK.sty, and found it in package texlive-cjk-2007-69.noarch.rpm which I install, even though I don't understand why I have to install CJK support to write in Spanish:
Me neither. I mean why you install CJK support for Spanish ;-)
It's crazy, isn't it?
I never asked myself what is necessary for browsing and what for writing. Maybe some of experts for printing can help us.
Maybe... I've never been able to make it work fully. If it wasn't one thing, it was another. I'm always hopping suse packagers will finally get it right one time, out of the box, or at least find a definitive document telling what exactly to install and what configuration file to modify and how exactly. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpdv/tTMYHG2NR9URAl7uAKCJBfR6qpvrw+9HutN0KJir4SiRtwCggmhh ji5ZPYNDTfEGwzel1h0vgVA= =ycjy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. schreef:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID:
Hi,
I'm trying to write an article using LyX.
I define the language as Spanish. I write a single word, "olé". I export to ascii, and I get "Ole'".
Hm. Suse 10.2, LyX 1.5.1-1.guru.suse102, tetex-3.0-60 here. No problems, but I *never* export to ascii, always to PDF. I can make an Olé by a multicharacter or with LateX \'e and both work. Regards, -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-03 at 16:09 +0100, Jos van Kan wrote:
I'm trying to write an article using LyX.
I define the language as Spanish. I write a single word, "olé". I export to ascii, and I get "Ole'".
Hm. Suse 10.2, LyX 1.5.1-1.guru.suse102, tetex-3.0-60 here. No problems, but I *never* export to ascii, always to PDF. I can make an Olé by a multicharacter or with LateX \'e and both work.
So, you are not using the suse package. Why? Is it known to be broken? However, my keyboard is Spanish, and I refuse to write "olé" or any other special letter in my keyboard by a roundabout method. I can not export to PDF. Not to dvi, ps, html... you name it. None works. I get the errors already explained. There is no 'tetex' installed here, and yast does not find it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpd63tTMYHG2NR9URAgh8AJ9hZWxgLeQJMvDbcze9qVQiO9gcsQCcC3kn pIIBT1vJkgKLpq/pgBNuzgA= =cCGk -----END PGP SIGNATURE-----
Carlos E. R. schreef:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2008-02-03 at 16:09 +0100, Jos van Kan wrote:
I'm trying to write an article using LyX.
I define the language as Spanish. I write a single word, "olé". I export to ascii, and I get "Ole'".
Hm. Suse 10.2, LyX 1.5.1-1.guru.suse102, tetex-3.0-60 here. No problems, but I *never* export to ascii, always to PDF. I can make an Olé by a multicharacter or with LateX \'e and both work.
So, you are not using the suse package. Why? Is it known to be broken?
However, my keyboard is Spanish, and I refuse to write "olé" or any other special letter in my keyboard by a roundabout method.
I can not export to PDF. Not to dvi, ps, html... you name it. None works. I get the errors already explained.
There is no 'tetex' installed here, and yast does not find it.
The reason that I use the guru package is that at the time of installation I needed 1.5 and the official suse package only offered 1.4.3. At this moment I see they offer 1.5.3, but I never got to upgrade, since the guru package worked OK. Tetex was renamed "texlive" in 10.3 says Google (sorry, didn't know that). LyX is a front end to Latex, without a working tex distribution installed it won't work. That's no doubt the reason you can't export to ps or pdf. Best regards, -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-03 at 17:00 +0100, Jos van Kan wrote:
There is no 'tetex' installed here, and yast does not find it.
The reason that I use the guru package is that at the time of installation I needed 1.5 and the official suse package only offered 1.4.3. At this moment I see they offer 1.5.3, but I never got to upgrade, since the guru package worked OK.
On occasion, I have compiled LyX myself, in an attempt to see if it worked better.
Tetex was renamed "texlive" in 10.3 says Google (sorry, didn't know that). LyX is a front end to Latex, without a working tex distribution installed it won't work. That's no doubt the reason you can't export to ps or pdf.
Ah, then texlive is installed. I assume latex/tex must work, but it doesn't matter: the working tex installation must be produced by Yast: I refuse to learn tex in order to get LyX running properly, that's a no-no. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpiAVtTMYHG2NR9URAunFAJwJK4v9A7BBGNAlnMD5jfLBcKvLYQCeJ9Zj bZQQymLrNMCKdnyoCJ0IPRE= =/0ka -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. schreef:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ah, then texlive is installed.
I assume latex/tex must work, but it doesn't matter: the working tex installation must be produced by Yast: I refuse to learn tex in order to get LyX running properly, that's a no-no.
Fair enough. Try this: \documentclass{article} \usepackage [spanish] {babel} \begin {document} !`Ol\'e mundo! \end{document} Store those five lines in a file ole.tex, do from the cli pdflatex ole.tex and tell me if you get a file ole.pdf and if not, what are the error messages. That at least should tell you whether you have a working TeX installation. Without that all bets are off. You're right btw, that Yast should provide you with a working TeX installation, if you install texlive. Regards, -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-04 at 00:03 +0100, Jos van Kan wrote:
I assume latex/tex must work, but it doesn't matter: the working tex installation must be produced by Yast: I refuse to learn tex in order to get LyX running properly, that's a no-no.
Fair enough. Try this:
\documentclass{article} \usepackage [spanish] {babel} \begin {document} !`Ol\'e mundo! \end{document}
Store those five lines in a file ole.tex, do from the cli
pdflatex ole.tex
and tell me if you get a file ole.pdf and if not, what are the error messages. That at least should tell you whether you have a working TeX installation.
Yes, that test works. The problems are more difficult to track than that, like LyX failing to produce output when I select UTF8 as the encoding, which according to the documentation should work. I had to go back to use latin1 instead, which seems to work - mostly. Or trying the docbook article template, which fails completely with: "An error occurred whilst running sgmltools -b dvi 'newfile1.sgml'", which is a lot of help: Traceback (most recent call last): File "/usr/bin/sgmltools", line 83, in <module> tool.processFile(curfile) File "/usr/share/sgml/misc/sgmltools/python/SGMLtools.py", line 230, in processFile dssslfile = utils.findStylesheet(stylesheet, self._aliases) File "/usr/share/sgml/misc/sgmltools/python/utils.py", line 307, in findStylesheet return findStylesheet(name, aliases) File "/usr/share/sgml/misc/sgmltools/python/utils.py", line 317, in findStylesheet raise IOError, "Couldn't resolve pubid [%s]" % id IOError: Couldn't resolve pubid ["-//SGMLtools//DOCUMENT Docbook Style Sheet for Print//EN"] Error: Cannot convert file - ---------------------------------------- Which somehow sounds familiar.
Without that all bets are off. You're right btw, that Yast should provide you with a working TeX installation, if you install texlive.
It is working, but not fully. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpmH1tTMYHG2NR9URAmTMAJ0WpsTB+yOJpu3l5TgtLX34XmoSqwCeK75v vDO5lbntqRcVSY47+UhwOJQ= =zOBf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Mon, 04 Feb 2008, Carlos E. R. wrote:
File "/usr/share/sgml/misc/sgmltools/python/utils.py", line 317, in findStylesheet raise IOError, "Couldn't resolve pubid [%s]" % id IOError: Couldn't resolve pubid ["-//SGMLtools//DOCUMENT Docbook Style Sheet for Print//EN"] Error: Cannot convert file
There's something amiss with your sgmltools installation, you're either missing the stylesheet, the sgml-catalog entry or possibly the permission to read the stylesheet / the catalog. I find in SuSE 10.2 the above pubid in the file /usr/share/sgml/stylesheets/sgmltools/sgmltools.cat out of the package sgmltools-lite, which points to a file 'print.dsl' out of the same package. If that's the reason, it's not a fault of any LyX or TeX package. HTH, -dnh -- Connection reset by beer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-02-05 at 01:54 +0100, David Haller wrote:
Hello,
On Mon, 04 Feb 2008, Carlos E. R. wrote:
File "/usr/share/sgml/misc/sgmltools/python/utils.py", line 317, in findStylesheet raise IOError, "Couldn't resolve pubid [%s]" % id IOError: Couldn't resolve pubid ["-//SGMLtools//DOCUMENT Docbook Style Sheet for Print//EN"] Error: Cannot convert file
There's something amiss with your sgmltools installation, you're either missing the stylesheet, the sgml-catalog entry or possibly the permission to read the stylesheet / the catalog.
I only installed what Yast installs. I have no idea what/how to configure nor what to install to make it work. I haven't seen a pattern or a list of packages or something to install whatever is needed to make LyX work out of the box.
I find in SuSE 10.2 the above pubid in the file /usr/share/sgml/stylesheets/sgmltools/sgmltools.cat out of the package sgmltools-lite, which points to a file 'print.dsl' out of the same package.
sgmltools-lite was not installed. I installed sgmltools, and I still got the same error. I then removed it and installed sgmltools-lite. Now there is no error, but the "dvi" output is totally incorrect (using the "docbook-article.lyx" template): TitleDateJoeDocAbstractFirst SectionFirst Paragraph That's the output I get, a single line, totally wrong. It should be a formatted text, with tittle, author, date, etc, in the correct places, fonts, sizes, etc. Looking at the output on the xterm (LyX is silent about errors) I see this jiberish: cer@nimrodel:~/Projects/babel/LyX> /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:11:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:13:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:14:2:E: unknown declaration type "attlist" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:18:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:19:2:E: unknown declaration type "attlist" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:22:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:23:2:E: unknown declaration type "attlist" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:29:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:34:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:39:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:44:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:46:2:E: unknown declaration type "attlist" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:52:2:E: unknown declaration type "element" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:53:2:E: unknown declaration type "attlist" /usr/bin/openjade:/usr/share/sgml/openjade/style-sheet.dtd:76:2:E: entity end not allowed in processing instruction /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:26:0:E: DTD did not contain element declaration for document type name /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:25:0:E: notation "dsssl" for entity "docbook.dsl" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:27:12:E: element "style-sheet" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:29:24:E: there is no attribute "id" /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:29:36:E: there is no attribute "use" /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:29:45:E: element "style-specification" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:30:25:E: element "style-specification-body" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:69:46:E: element "style-specification" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:70:25:E: element "style-specification-body" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:75:47:E: element "style-specification" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:76:25:E: element "style-specification-body" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:81:43:E: element "style-specification" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:82:25:E: element "style-specification-body" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:105:27:E: there is no attribute "id" /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:105:46:E: there is no attribute "document" /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:105:59:E: element "external-specification" undefined /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:106:13:E: end tag for "external-specification" omitted, but OMITTAG NO was specified /usr/bin/openjade:/usr/share/sgml/stylesheets/sgmltools/print.dsl:105:0: start tag was here /usr/bin/openjade:E: specification document does not have the DSSSL architecture as a base architecture /usr/bin/openjade:E: no style-specification or external-specification with ID "print" This is pdfTeX, Version 3.141592-1.40.3 (Web2C 7.5.6) entering extended mode (/tmp/tmpEKqNcu JadeTeX 2003/04/27: 3.13 (/usr/share/texmf/tex/latex/psnfss/t1ptm.fd) Elements will be labelled ! LaTeX Error: Missing \begin{document}. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.8 {2}}T itle\endNode{}\Node% \HyPL@Entry{0 << /S /D >> } [1.0.52] ! I can't find file `tmpEKqNcu.aux'. \enddocument ...makeatletter \input \jobname .aux \fi \@dofilelist \ifdim \f... l.26 ...ode{}\endNode{}\endNode{}\endNode{}\endFOT {} Please type another input file name ! Emergency stop. \enddocument ...makeatletter \input \jobname .aux \fi \@dofilelist \ifdim \f... l.26 ...ode{}\endNode{}\endNode{}\endNode{}\endFOT {} Output written on tmpEKqNcu.dvi (1 page, 1856 bytes). Transcript written on tmpEKqNcu.log. This is pdfTeX, Version 3.141592-1.40.3 (Web2C 7.5.6) entering extended mode (/tmp/tmpEKqNcu JadeTeX 2003/04/27: 3.13 (/usr/share/texmf/tex/latex/psnfss/t1ptm.fd) Elements will be labelled ! LaTeX Error: Missing \begin{document}. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.8 {2}}T itle\endNode{}\Node% \HyPL@Entry{0 << /S /D >> } [1.0.52] ! I can't find file `tmpEKqNcu.aux'. \enddocument ...makeatletter \input \jobname .aux \fi \@dofilelist \ifdim \f... l.26 ...ode{}\endNode{}\endNode{}\endNode{}\endFOT {} Please type another input file name ! Emergency stop. \enddocument ...makeatletter \input \jobname .aux \fi \@dofilelist \ifdim \f... l.26 ...ode{}\endNode{}\endNode{}\endNode{}\endFOT {} Output written on tmpEKqNcu.dvi (1 page, 1856 bytes). Transcript written on tmpEKqNcu.log. This is pdfTeX, Version 3.141592-1.40.3 (Web2C 7.5.6) entering extended mode (/tmp/tmpEKqNcu JadeTeX 2003/04/27: 3.13 (/usr/share/texmf/tex/latex/psnfss/t1ptm.fd) Elements will be labelled ! LaTeX Error: Missing \begin{document}. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.8 {2}}T itle\endNode{}\Node% \HyPL@Entry{0 << /S /D >> } [1.0.52] ! I can't find file `tmpEKqNcu.aux'. \enddocument ...makeatletter \input \jobname .aux \fi \@dofilelist \ifdim \f... l.26 ...ode{}\endNode{}\endNode{}\endNode{}\endFOT {} Please type another input file name ! Emergency stop. \enddocument ...makeatletter \input \jobname .aux \fi \@dofilelist \ifdim \f... l.26 ...ode{}\endNode{}\endNode{}\endNode{}\endFOT {} Output written on tmpEKqNcu.dvi (1 page, 1856 bytes). Transcript written on tmpEKqNcu.log. cer@nimrodel:~/Projects/babel/LyX>
If that's the reason, it's not a fault of any LyX or TeX package.
I don't know who is at fault, only that the "docbook-article.lyx" fails completely to produce any usable output. :-/ What do I do to repair it? What do I install/remove? What Yast installed does not work, and I have absolutely no idea how to repair it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHp8c4tTMYHG2NR9URAlMwAJwPWZoUY5wG9NbUb90xk+ooldAfAACfXmgD JxkVoDQcZsJLn2Mh6RCNNaw= =wBvP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 03 February 2008, Carlos E. R. wrote:
Content-ID:
Hi,
I'm trying to write an article using LyX.
I define the language as Spanish. I write a single word, "olé". I export to ascii, and I get "Ole'".
Useless.
Tex doesn't support unicode. There have been attempts to rewrite tex with full support for unicode (omega - abandoned, xetex - in development), you might have better results with them. There are ways to make tex work for a specific language, they aren't proper solutions though. You may also try to set your input encoding to something other than unicode.
I then specify "utf8". Now, when converting, I get a pop window that says "an empty ouput file was generated", and then another "LaTeX Error: file 'CJK.sty' not found ".
I don't know what this is about.
I search for CJK.sty, and found it in package texlive-cjk-2007-69.noarch.rpm which I install, even though I don't understand why I have to install CJK support to write in Spanish:
Description : CJK LaTeX is a macro package for LaTeX to enable typesetting Chinese, Japanese, and Korean. It supports (simultaneously) various CJK encodings, such as Big5, GB, JIS, KS, and CNS.
It doesn't do any good: I still get the same error in LyX, and I can't get any output whatsoever in any format.
As always, LyX fails very short of the mark: it is useless. At least in SuSE.
This isn't a suse specific problem.
How can I get LyX to work? I have _never_ been able to get LyX to really work (in years). I suppose it works somewhere, but for me, that I have no idea of Tex and that I simply want it to work out of the box, it has never worked. Never, since suse 5 or 6. And I keep trying because I like the idea...
Try typing ASCII characters with latex markup (\"o, \'e etc).
(I'll try removing anything related to lyx and tex and reinstalling. Who knows.)
[...]
Same thing: doesn't work, different symptoms.
With one document:
- export to plain text (ps2ascii) uses incorrect tildes. - export to plain text, now is more correct, but if I use "insert program listing", the listing does not get the to the output.
With another document (ie, one with more than a single word), I still get "LaTeX Error: file 'CJK.sty' not found" (and I don't have any idea of eastern languages). On the xterm I see:
Could not find LaTeX command for character 0xfffd. LaTeX export will fail.
How can I find and remove that char, or otherwise configure lyx to forget that char and write a "?" in its place, or whatever is needed for it to work?
I create a new empty document, using the "docbook_article" template, and try to produce output, and it fails - as always:
An error occurred whilst running sgmltools -b dvi 'newfile1.sgml' Traceback (most recent call last): File "/usr/bin/sgmltools", line 83, in <module> tool.processFile(curfile) File "/usr/share/sgml/misc/sgmltools/python/SGMLtools.py", line 230, in processFile dssslfile = utils.findStylesheet(stylesheet, self._aliases) File "/usr/share/sgml/misc/sgmltools/python/utils.py", line 307, in findStylesheet return findStylesheet(name, aliases) File "/usr/share/sgml/misc/sgmltools/python/utils.py", line 317, in findStylesheet raise IOError, "Couldn't resolve pubid [%s]" % id IOError: Couldn't resolve pubid ["-//SGMLtools//DOCUMENT Docbook Style Sheet for Print//EN"] Error: Cannot convert file
and nothing is created.
Lyx is useless, and I'm very frustrated :-(
In order to use lyx, you should be familiar with the tex system. I have used omega with unicode text successfully, I haven't had much success with xetex. Best regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-03 at 20:31 +0200, auxsvr@gmail.com wrote:
Tex doesn't support unicode. There have been attempts to rewrite tex with full support for unicode (omega - abandoned, xetex - in development), you might have better results with them. There are ways to make tex work for a specific language, they aren't proper solutions though. You may also try to set your input encoding to something other than unicode.
Damm! No utf. :-/ omega abandoned? Then I'd better remove it. I'll install xetex instead. Otherwise, I'l have to try using latin1 instead of utf. [...] Yep, the document works better in that format. I set UTF because one of the error/warning messages sugested me to use it, and because the original palin document I started from was utf. Interestingly, the conversion to text produces an utf plain text file.
I then specify "utf8". Now, when converting, I get a pop window that says "an empty ouput file was generated", and then another "LaTeX Error: file 'CJK.sty' not found ".
I don't know what this is about.
Probably a by-product of using utf.
How can I get LyX to work? I have _never_ been able to get LyX to really work (in years). I suppose it works somewhere, but for me, that I have no idea of Tex and that I simply want it to work out of the box, it has never worked. Never, since suse 5 or 6. And I keep trying because I like the idea...
Try typing ASCII characters with latex markup (\"o, \'e etc).
No, that's absolutely out of the question. Either it works using my existing keyboard, or I use something else, like openoffice.
Lyx is useless, and I'm very frustrated :-(
In order to use lyx, you should be familiar with the tex system. I have used omega with unicode text successfully, I haven't had much success with xetex.
I have no idea of tex, nor I want to. For instance, I do not need to know XML to get OpenOffice write documents, and I expect the same of LyX: I have no reason to learn Tex either. That's the job of Lyx and the packagers, not mine. :-/ - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHph49tTMYHG2NR9URAmCLAJ41p3/8GN1I6BWMT44kdKf73ZKXhwCfeXYs kzfcTdHIE+z7rxueFQk1EM4= =cblD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Sun, 03 Feb 2008, auxsvr@gmail.com wrote:
Tex doesn't support unicode.
Inputenc supports UTF-8 for quite a while now. \usepackage[utf8]{inputenc} You have to be careful though, there was a conflict of utf8.def between inputenc and ucs, IIRC. The TeX-FAQ should tell more. The following should work: ==== testutf8.tex ===== \documentclass{scrartcl} \usepackage{lmodern} \usepackage[utf8]{inputenc} \listfiles \begin{document} äöüß \end{document} ==== pdflatex testutf8.tex xpdf testutf8.pdf If this does not work, you should mail the error message and the output of the listfiles command at the end of the log. -dnh -- You are wise, witty, and wonderful, but you spend too much time reading this sort of trash. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-04 at 03:00 +0100, David Haller wrote:
On Sun, 03 Feb 2008, auxsvr@gmail.com wrote:
Tex doesn't support unicode.
Inputenc supports UTF-8 for quite a while now.
\usepackage[utf8]{inputenc}
You have to be careful though, there was a conflict of utf8.def between inputenc and ucs, IIRC.
The TeX-FAQ should tell more.
The following should work:
==== testutf8.tex ===== \documentclass{scrartcl} \usepackage{lmodern} \usepackage[utf8]{inputenc} \listfiles \begin{document} äöüß \end{document} ====
pdflatex testutf8.tex xpdf testutf8.pdf
If this does not work, you should mail the error message and the output of the listfiles command at the end of the log.
Yes, it works, today - after I unistalled it all yesterday and reinstalled. This is what I have currently installed: Sun Feb 03 2008 Sat Sep 22 2007 texlive-bin 2007-68 i586 http://bugs.opensuse.org Sun Feb 03 2008 Sun Sep 23 2007 latex2html-pngicons 2002.2.1-478 noarch http://bugs.opensuse.org Sun Feb 03 2008 Wed Oct 03 2007 texlive 2007-69.2 noarch http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 dviutils 94.3.19-1114 i586 http://bugs.opensuse.org Sun Feb 03 2008 Wed Sep 26 2007 kdegraphics3-tex 3.5.7-60 i586 http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 texlive-bin-latex 2007-68 i586 http://bugs.opensuse.org Sun Feb 03 2008 Wed Oct 03 2007 texlive-latex 2007-69.2 noarch http://bugs.opensuse.org Sun Feb 03 2008 Wed Sep 26 2007 kile 1.9.3-99 i586 http://bugs.opensuse.org Sun Feb 03 2008 Tue Sep 25 2007 lyx 1.5.1-28 i586 http://bugs.opensuse.org Sun Feb 03 2008 Sun Sep 23 2007 latex2html 2002.2.1-478 noarch http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 sgml-skel 0.6-346 noarch http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 iso_ent 2000.11.03-736 noarch http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 xmlcharent 0.3-335 noarch http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 docbook_5 5.0CR4-27 noarch http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 docbook5-xsl-stylesheets 1.73.1-10 noarch http://bugs.opensuse.org Sun Feb 03 2008 Wed Oct 03 2007 texlive-context 2007-69.2 noarch http://bugs.opensuse.org Sun Feb 03 2008 Sat Sep 22 2007 texlive-bin-xetex 2007-68 i586 http://bugs.opensuse.org but the docbook template still doesn't work, and the conversion to plain text has problems and failures. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpt9stTMYHG2NR9URAks9AJwN3MO0V8WcLBH+ZvU7U+QfDQT6/ACcCIRK nyvB3DMTGyIE6r0we7PVqMQ= =O+hU -----END PGP SIGNATURE-----
On Monday 04 February 2008 02:48, Carlos E. R. wrote:
Sun Feb 03 2008 Sat Sep 22 2007 texlive-bin 2007-68 i586 http://bugs.opensuse.org
OK, I'm curios, Why are there packages coming from bugs.opensuse.org? Is that where the bugs get put in :-) -- Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-02-04 at 05:33 -0700, Don Raboud wrote:
On Monday 04 February 2008 02:48, Carlos E. R. wrote:
Sun Feb 03 2008 Sat Sep 22 2007 texlive-bin 2007-68 i586 http://bugs.opensuse.org
OK, I'm curios,
Why are there packages coming from bugs.opensuse.org?
Is that where the bugs get put in :-)
Now that you mention... I have no idea. Thats's what the {PACKAGER} field of the rpm database contains: Name : texlive-bin Relocations: (not relocatable) Version : 2007 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 68 Build Date: Sat Sep 22 06:28:18 2007 Install Date: Sun Feb 3 12:23:05 2008 Build Host: hammer14.suse.de Group : Productivity/Publishing/TeX/Base Source RPM: texlive-bin-2007-68.nosrc.rpm Size : 6748092 License: GPL v2 or later, TeX-License Signature : DSA/SHA1, Sat Sep 22 06:30:42 2007, Key ID a84edae89c800aca Packager : http://bugs.opensuse.org <============== URL : http://www.tug.org/texlive/ Summary : The Base System of TeXLive Description : After installing texlive and the package texlive-latex, find a large selection of documentation for TeX, LaTeX, and various layout styles in /usr/share/texmf/doc. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpxJltTMYHG2NR9URAg0UAJ0WzQ/EnEJ+WYYK/Bp1lBjnjQ01twCfdlOE P2RJ+Gc91/D+piz/4TQ/Ob8= =0xTe -----END PGP SIGNATURE-----
Hello, On Monday 04 February 2008, David Haller wrote:
Hello,
On Sun, 03 Feb 2008, auxsvr@gmail.com wrote:
Tex doesn't support unicode.
Inputenc supports UTF-8 for quite a while now.
It only supports a subset of UTF-8, as Tex wasn't designed to support 16 bit fonts. It's a design limitation.
\usepackage[utf8]{inputenc}
You have to be careful though, there was a conflict of utf8.def between inputenc and ucs, IIRC.
The TeX-FAQ should tell more.
The following should work:
==== testutf8.tex ===== \documentclass{scrartcl} \usepackage{lmodern} \usepackage[utf8]{inputenc} \listfiles \begin{document} äöüß \end{document} ====
pdflatex testutf8.tex xpdf testutf8.pdf
If this does not work, you should mail the error message and the output of the listfiles command at the end of the log.
This does work. Probably even spanish accents work, so this may help Carlos. However, this doesn't mean that unicode is supported, which can be verified easily by typing the € (euro character) or characters of most other scripts in the world. Best regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
This does work. Probably even spanish accents work, so this may help Carlos. However, this doesn't mean that unicode is supported, which can be verified easily by typing the € (euro character) or characters of most other scripts in the world.
The euro and the accents seems to work, so I'm happy at last. My guess is that the character '0xfffd' got into the file some how (or into the configuration files), and this character must be CJK (Eastern): ] Could not find LaTeX command for character 0xfffd. ] LaTeX export will fail. That's why LyX said it wanted "CJK.sty": ] "LaTeX Error: file 'CJK.sty' not found " but even when I installed it, it failed. It suddenly began to work after I had removed all tex, latex, and lyx related files, reinstalled, and who knows what else I did. It is finally working, except docbook. But that has never worked. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHp4EgtTMYHG2NR9URAiclAJ4wyOwmSVnUsOu1FOCL6Ki/33KelgCeOmd0 CyZc41kdqSzA6OPiIFrWuEk= =hRJO -----END PGP SIGNATURE-----
Hello, On Mon, 04 Feb 2008, auxsvr@gmail.com wrote:
On Monday 04 February 2008, David Haller wrote:
Hello,
On Sun, 03 Feb 2008, auxsvr@gmail.com wrote:
Tex doesn't support unicode.
Inputenc supports UTF-8 for quite a while now.
It only supports a subset of UTF-8,
UTF-8 is an encoding of a character-set, not a character-set. And LaTeX supports a huge part of unicode. The bigger problem is finding fonts which contain the glyphs.
as Tex wasn't designed to support 16 bit fonts. It's a design limitation.
TeX uses many different fonts anyway, most traditional fonts are only 7-bit. This has no influence whatsoever on what glyphs LaTeX supports. E.g. traditional TeX uses 7-bit encodings and 7-bit fonts and supports many more glyphs (more than latin1 + at least 256 math signs).
This does work. Probably even spanish accents work, so this may help Carlos. However, this doesn't mean that unicode is supported, which can be verified easily by typing the €= (euro character) or characters of most other scripts in the world.
You need to use packages to support the characters. E.g: ==== \documentclass{scrartcl} \usepackage{lmodern} \usepackage{textcomp} \usepackage[utf8]{inputenc} \listfiles \begin{document} äöü߀óéñõ\end{document} ==== You need textcomp for \texteuro. You'll need CJK or something for asian characters, etc. If it doesn't work for you, you're missing something (in the log or a package or ...). BTW: I use a quite old TeX (teTeX 2.0.9 IIRC), with some updated packages. And the above works for me. -dnh -- There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence. -- Jeremy S. Anderson -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sun, 03 Feb 2008, by robin.listas@telefonica.net:
Content-ID:
Hi,
I'm trying to write an article using LyX.
I define the language as Spanish. I write a single word, "olé". I export to ascii, and I get "Ole'".
Of course, ASCII is not ment to "know" about comp[osed characters etc.
Useless.
Your action is, yes. Why not just export as tex file? $ cat newfile1.tex %% LyX 1.5.3 created this file. For more info, see http://www.lyx.org/. %% Do not edit unless you really know what you are doing. \documentclass[spanish]{article} \usepackage[T1]{fontenc} \usepackage[latin9]{inputenc} \makeatletter \usepackage{babel} \deactivatetilden \makeatother \begin{document} ol\'e \end{document} Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 10.3 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.22 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
I'm trying to write an article using LyX.
I define the language as Spanish. I write a single word, "olé". I export to ascii, and I get "Ole'".
Of course, ASCII is not ment to "know" about comp[osed characters etc.
Whatever the name is. I want a plain text file in utf-8. This is the file created from LyX in latin1 enconding: cer@nimrodel:~/Projects/babel/LyX> file Readme_es.txt xine-ui.cvs.Readme_es.txt: UTF-8 Unicode text However, if I use utf8 encoding in the LyX file, it fails to produce any output.
Useless.
Your action is, yes. Why not just export as tex file?
Because what I want this time is text, not tex. Because it failed with ""LaTeX Error: file 'CJK.sty' not found ", even when that file existed. Now my file is in latin1, and after I uninstalled everything related to lyx and tex, and reinstalled, it seems to work better - with a lot of quirks that I'll probably have to edit directly in the output. For instance, "notes" that are not displayed in the dvi page (correct) appear on the plain text one (incorrect). Or code inserts that are not output to the text file. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHpmuYtTMYHG2NR9URAlN8AJ9lBZ+ya9jNUSPKuhFKF7cwBN2xRQCfZDuO 4s8FWnwndETF/io0v3no3qU= =roqo -----END PGP SIGNATURE-----
participants (7)
-
auxsvr＠gmail.com -
Carlos E. R. -
David Haller -
Don Raboud -
Jos van Kan -
Rajko M. -
Theo v. Werkhoven