[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gimp-print-devel
Subject:    Re: [Gimp-print-devel] I18N
From:       Michael Sweet <mike () easysw ! com>
Date:       2001-01-31 15:54:59
[Download RAW message or body]

Roger Leigh wrote:
> ...
> OK. I was not going to do anything at all with CUPS or the
> ghostscript driver at this point. From what Michael Sweet said
> earlier, I think the CUPS i18n code will be based on the i18n
> mechanism actually used in the CUPS core, which uses integers and
> not gettext (it is a small catalogue IIRC). I was just going to
> convert libgimpprint, escputil, print (already done?) (and possibly
> test/*). I don't know how ghostscript does things.

It doesn't, and if you do any localization stuff it will cause
major problems for things like "," instead of "." for the decimal
point in numbers, etc.  We force the POSIX locale in our version
of Ghostscript to avoid this problem...

As for CUPS (and potentially Ghostscript) PPD files, the genppd
program still needs to lookup the localized strings when creating
the PPD files, but those can be (and should be) the same catalogs
used by the GIMP plug-in.

> ...
> (PIC code discussion deleted)
> ...

FWIW, the penalty for using PIC code all the time is not incredibly
high.  My recommendation is to compile everything as PIC code if
you are building shared libraries - this avoids any nasty issues
and will make the build process a lot simpler and easier to
maintain.

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products                  mike@easysw.com
Printing Software for UNIX                       http://www.easysw.com

_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/gimp-print-devel

[prev in list] [next in list] [prev in thread] [next in thread]