[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Palettes and libraries.. (was Re: Interface localization ?)

From: Gregory John Casamento
Subject: Re: Palettes and libraries.. (was Re: Interface localization ?)
Date: Sun, 25 Nov 2007 11:46:08 -0800 (PST)


Not hard at all.  I've considered the idea of creating a "nibtool" equivalent.  
 Since GormLib (InterfaceBuilder.framework) and GormCore are both libraries, 
such a tool could easily link to them and have most of the functionality of 
Gorm on the command-line.

The limiting factor for me has only been time.

Gregory Casamento -- OLC, Inc 
# GNUstep Chief Maintainer

----- Original Message ----
From: David Chisnall <address@hidden>
To: GNUstep Discuss <address@hidden>
Sent: Sunday, November 25, 2007 2:09:32 PM
Subject: Re: Palettes and libraries.. (was Re: Interface localization ?)

Hi Gregory,

On 25 Nov 2007, at 18:42, Gregory John Casamento wrote:

> As far as interface localization goes, Gorm has a Translate feature  
> under the Document menu which allows you to export the existing  
> strings in the interface and create a strings file.   This feature  
> will allow you to provide the translations and then load the strings
> back and Gorm will replace the strings with the translations  
> provided.   Granted it's not dynamic, but my feeling is that, if I  
> have one interface for all languages, is it necessarily appropriate  
> for all for all of them?

How hard would it be to put this functionality into a command-line  
tool equivalent to Apple's nibtool?  It would be nice to have this  
integrated into a build system so that changes to strings in a gorm  
file could automatically be flagged for translators by an automated  
build process.


Discuss-gnustep mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]