>>>>> "Kevin" == Kevin Paunovic <[EMAIL PROTECTED]> writes:
Hello,
Kevin> When exporting a LyX file to latex (pdflatex) in MacOSX, the
Kevin> .tex file is encoded using Western MacOS Roman but the .tex
Kevin> file declares \usepackage[latin1]{inputenc} (it should be
Kevin> applemac and not latin1). I tried to specify applemac with no
Kevin> luck: one can only choose between latin1, latex default (ie
Kevin> nothing), and some codepages (no cp1252). Does anyone know how
Kevin> to do this?
I thought mac os x was latin1-based. Do you really need applemac?
Kevin> Is there a way to teach LyX to use common characters when
Kevin> possible while exporting? Mine transforms double quotes to
Kevin> \char`\"{} instead of using the " char.
This is a particular case, meant to work around the fact that
babel/german likes to make " active for various uses (as a shortcut
macro, actually), and this obviously does not fit well with what we
want to do.
We should definitely find a better solution, but nobody took the time
to do that.
Kevin> Another problem with quotes: I checked the document option to
Kevin> use English opening and closing double quotes (``and '') but
Kevin> when exported to latex, my .tex file contains those "quotes"
Kevin> (straight). It would be great if either LyX exports ``quotes''
Kevin> like this (latex style), or "quotes" like this
All the quotes entered inside LyX will be in the form you describe
above.
Kevin> and uses csquotes package, making double quotes active.
I do not know much about this package, but packages that make
characters active make me nervous as far as LyX is concerned.
JMarc
