From: Till Kamppeter <till.kamppeter@gmx.net>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: Wendy Phillips <wendyp@sun.com>,
Norm Jacobs <Norm.Jacobs@Sun.COM>,
'Michael Sweet' <mike@easysw.com>,
printing-architecture <printing-architecture@freestandards.org>
Subject: Re: [Printing-architecture] Notes of today's telecon
Date: Fri, 26 May 2006 19:42:16 +0200 [thread overview]
Message-ID: <44773DF8.9010802@gmx.net> (raw)
In-Reply-To: <789E617C880666438EDEE30C2A3E8D10EE1E@mailsrvnt05.enet.sharplabs.com>
McDonald, Ira wrote:
> Hi,
>
> I'm going to support Michael's point here. The prevailing
> usage in the localization industry and in most file systems
> is to use language tag directories immediately _before_ the
> terminal filename in a path.
>
So you suggest
/usr/share/ppd/foomatic/HP/en/HP-LaserJet_4050-ljet4-en.ppd
/usr/share/ppd/foomatic/HP/en/HP-LaserJet_4050-pxlmono-en.ppd
/usr/share/ppd/foomatic/HP/en/HP-LaserJet_4050-hpijs-en.ppd
/usr/share/ppd/gutenprint/HP/en/HP-LaserJet_4050-standard-en.ppd
/usr/share/ppd/gutenprint/HP/en/HP-LaserJet_4050-simplified-en.ppd
/usr/share/ppd/gutenprint/HP/de/HP-LaserJet_4050-simplified-de.ppd
Is this what you mean?
Having the language directory as the last level makes it also easier to
install (and also to uninstall) selected languages.
> And leaving aside "extra" entirely (not that we should),
> 10,000 printers with typically 10 languages supported
> makes a directory of 100,000 PPDs with the language tag
> as a suffix in the terminal filename - awful performance
> for search and installation tools.
>
Or should we do
/usr/share/ppd/gutenprint/HP/LaserJet_4050/simplified/de/HP-LaserJet_4050-simplified-de.ppd
but we must read the PPDs anyway to match the detected printer against
the device ID strings in them.
> Though an installation tool MIGHT have to search multiple
> directories for a given model, it could easily check the
> user's current locale and present as the default (before
> ANY other searching) a PPD for the current locale.
>
This reduces search time a lot, and by not installing unneeded language
directories one can save a lot of disk space.
> I sympathize with Glen about standardizing "extra", but
> I tend to think it's mostly hopeless - syntax yes, content
> not worth the effort.
Some tag in "Extra" telling the meaning of the content (like a "d_" for
a driver name) could make things easier, but it is not absolutely needed.
Till
next prev parent reply other threads:[~2006-05-26 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 16:59 [Printing-architecture] Notes of today's telecon McDonald, Ira
2006-05-26 17:42 ` Till Kamppeter [this message]
2006-05-26 17:52 ` Michael Sweet
-- strict thread matches above, loose matches on Subject: below --
2006-05-29 18:30 McDonald, Ira
2006-05-26 14:10 Petrie, Glen
2006-05-25 22:31 Norm Jacobs
2006-05-26 0:18 ` Till Kamppeter
2006-05-26 14:43 ` Michael Sweet
2006-05-25 14:57 McDonald, Ira
2006-05-24 22:51 Till Kamppeter
2006-05-25 14:28 ` Till Kamppeter
[not found] ` <44750622.2050005@sun.com>
2006-05-25 14:32 ` Till Kamppeter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44773DF8.9010802@gmx.net \
--to=till.kamppeter@gmx.net \
--cc=Norm.Jacobs@Sun.COM \
--cc=imcdonald@sharplabs.com \
--cc=mike@easysw.com \
--cc=printing-architecture@freestandards.org \
--cc=wendyp@sun.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.