so we would have, for example:

ted-cs  (for Czech)
ted-en-gb (for UK English)
ted-en-us (for US English),

etc. right?  

Now for the $100k question.  Do these packages go in 'textproc'
because thats where ispell is, or in 'print' because thats where ted the
program is.  Now I am wishing I had put ted into 'textproc' to start
with....

-Dan

On Wed, 15 Sep 1999, Kimmo Suominen wrote:

> One idea might be using the language codes from /usr/share/misc/language
> and stick to them throughout pkgsrc in the future.  For country codes I'd
> use the two letter codes from /usr/share/misc/country (same as the top-
> level domains).
> 
> I like the short codes so the package names don't end up overly long (more
> space is left available for the basename of the package), and these codes
> are already familiar from locale settings to many users.
> 
> Cheers,
> + Kim
> 
> 

> mcmahill@mtl.mit.edu writes:
> 
> | Anyway, is there a standard naming convention for stuff like that?  Right
> | now I have:
> | 
> | the dictionary packages:
> | 
> | ted-Czech
> | ted-Danish
> | ted-Dutch
> | ted-French
> | ted-German
> | ted-Italian
> | ted-Norwegian
> | ted-Portuguese
> | ted-Spanish
> | ted-Swedish
> | ted-UK_English
> | ted-US_English