Le 10 avr. 09 à 18:34, Jürgen Spitzmüller a écrit :
Jean-Marc Lasgouttes wrote:
And a couple of different packages for specific tasks (font
handling,
language support, color handling etc.). Of course it's not as far
apart as context, which is a different macro language to tex, but
still it's significantly more apart than pdflatex, because latex and
pdflatex have the same range of packages, while xetex differs. It's
something "inbetween".
Looks still like a flavor to me :)
Would it lower your confusion about the param+flavor pair if I
renamed the
useXetex param to useSystemFonts?
Maybe, maybe not. I began to look at the "special" formats and I am
wondering
from where to start.
So as a preamble, is there a reason why getOUtputFormat, instead of
looking
at various hardcoded variables, could not be written like the following?
string Buffer::getDefaultOutputFormat() const
{
string format = lyxrc.default_view_format;
if (!params().defaultOutputFormat.empty()
&& params().defaultOutputFormat != "default")
format = params().defaultOutputFormat;
if (isExportable(format))
return format;
typedef vector<Format const *> Formats;
Formats const formats = exportableFormats(true);
if (formats.empty())
return string();
// return the first we find
return formats.front()->name();
}
JMarc
