On Thu, Feb 03, 2000 at 01:17:45AM +0100, [EMAIL PROTECTED] wrote:
So that means that we need a new domain, such as "gimp-override",
that resides in .gimp/locale and is consulted just like gimp-perl and
gimp-plug-ins.
No
You seem to want to move the catalogs to the home directorys,
On 3 Feb, Marc Lehmann wrote:
Hmm... I removed gimp-perl.pot now. However, all the other .pot files
_are_ in cvs.
Shouldn't be, the files are generated at compile time and ignored by
CVS...
Whats the logic behind that?
Server:/usr/src/gimp/po # less .cvsignore
*.gmo
*.mo
Makefile
On 3 Feb, Marc Lehmann wrote:
You seem to want to move the catalogs to the home directorys, which is
much worse (one copy for each user is insane).
But would work
Do you have any _reasons_ not having a seperate domain (speed?
usability?) AFAIK it'S only in a few places neede
On Fri, Feb 04, 2000 at 01:11:44AM +0100, [EMAIL PROTECTED] wrote:
You seem to want to move the catalogs to the home directorys, which is
much worse (one copy for each user is insane).
But would work
Just as the other way woudl. But it would save 3MB of space. Given that
many people
On Fri, Feb 04, 2000 at 01:13:40AM +0100, [EMAIL PROTECTED] wrote:
Shouldn't be, the files are generated at compile time and ignored by
CVS...
Whats the logic behind that?
Server:/usr/src/gimp/po # less .cvsignore
gimp.pot
Ok... Sven?? Shouldn't these be deleted?
--
Daniel, do you know how to modify the Makefiles to do that, and where
a good place to store these files is (probably just besides the .mo
files)? There must be a simple way to find them though (a gimptool switch,
maybe)?
Sven??
Sorry, Gimp-1.2 first.
Salut, Sven
Hi,
Before you start to go crazy about post-1.2 i18n issues,
wouldn't it be nice to first clean up the situation for
gimp-1.1 a bit? I'm speaking about the UI and translation
of the perl plug-in.
The po directory has a totally different mechanism for
storing and building the po and mo files
On 2 Feb, Marc Lehmann wrote:
Well, yes, but I guess they wouldn't want to translated them
themselves, so why personal i.e. with catalog in the home directory?
Because it's the only user-writable place on a machine. I only talk
about installing plug-ins _seperately_ from the gimp.
On Wed, Feb 02, 2000 at 03:28:46PM +0100, [EMAIL PROTECTED] wrote:
You can create domains with nearly no limit. Where the files
reside is completely up to, it may even be the homedirectory...
So that means that we need a new domain, such as "gimp-override",
that resides in .gimp/locale and
On Wed, Feb 02, 2000 at 11:16:44AM +0100, Sven Neumann [EMAIL PROTECTED]
wrote:
Before you start to go crazy about post-1.2 i18n issues,
wouldn't it be nice to first clean up the situation for
gimp-1.1 a bit?
The usual situation: I can't fix problems that I do not know about. So
just tell
On 2 Feb, Marc Lehmann wrote:
So that means that we need a new domain, such as "gimp-override",
that resides in .gimp/locale and is consulted just like gimp-perl and
gimp-plug-ins.
No
The command you're asking for is msgunfmt...
Hmm... sounds like the solution. You pribably made
On Tue, Feb 01, 2000 at 09:12:31PM +0100, [EMAIL PROTECTED] wrote:
users want translated plug-ins! wether they come with the gimp or not.
Well, yes, but I guess they wouldn't want to translated them
themselves, so why personal i.e. with catalog in the home directory?
Because it's the
12 matches
Mail list logo
