Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 243382 - texlive-formatsextra - eplain non-portable language selection
Summary: texlive-formatsextra - eplain non-portable language selection
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Alexis Ballier
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-23 13:11 UTC by Helmut Jarausch
Modified: 2008-12-08 08:22 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Jarausch 2008-10-23 13:11:50 UTC
It seems to be impossible to use the eplain format (from exlive-formatsextra)
in portable way.
Reason: it's missing (some of) etex's language selection features.
E.g. for selecting the German hyphenation patterns I'd like to use
\uselanguage{ngerman}

or at least
\language=\lang@ngerman

The first macro isn't defined in the eplain format,
neither the controlsequence \lang@ngerman

So I'm stuck with looking at
/var/lib/texmf/web2c/pdftex/eplain.log
finding out the NUMBER of the ngerman patterns and using
\language=NUMBER

Truely not portable.


Reproducible: Always
Comment 1 Wormo (RETIRED) gentoo-dev 2008-10-25 07:30:26 UTC
This will probably turn out to be more of a feature request for the upstream project. Assigning to tex team, who can forward the request or suggest where you could post one yourself.
Comment 2 Alexis Ballier gentoo-dev 2008-10-26 15:12:40 UTC
(In reply to comment #0)
> Truely not portable.

I agree, but have you tried asking on tex-related mailing lists as I suggested in my mail ? This sounds more like the normal and wanted behavior for eplain to me :/
Comment 3 Alexis Ballier gentoo-dev 2008-12-08 08:22:12 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > Truely not portable.
> 
> I agree, but have you tried asking on tex-related mailing lists as I suggested
> in my mail ? This sounds more like the normal and wanted behavior for eplain to
> me :/


closing as upstream, this seems the normal behavior; please reopen if there is anything to fix