Subject: Re: menus and languages
From: sam th (firstname.lastname@example.org)
Date: Thu Feb 10 2000 - 15:45:37 CST
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 10 Feb 2000, [iso-8859-1] Joaquín Cuenca Abela wrote:
> sam th wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > As Mr Kerr seems no longer to be with us on the list, I decided to try to
> > work on the word count POW. However, in creating the new menus suggested
> > by Shaw in the original message, I discovered that in order to compile the
> > menu code, it is neccessary to have all the translations match the overall
> > menu layout. In order to get mine to compile, I commented out all the
> > other languages, but this is not a viable solution. Thus, I wonder if
> > anyone has a strategey for compiling without updating all the other
> > translations, or alternatively would like to translate the new menu items.
> > I would be happy to do the coding involved, if someone in the know would
> > explain to me what would need to be done.
> Use-gettext (tm).
> I don't understand why we are not using gettext. If the answer is...
> "portability issues", it's good to know that gettext works in unix AND
> in windows --and I think that a BeOS version should be something fairly
> trivial to do--. If the answer is... "nobody has come with a nice
> patch", then I can understand it :)
> Joaquín Cuenca Abela
> e-mail: email@example.com
Maybe I don't understand your suggestion, but I think I was not clear in
my statement of the problem. Here goes:
In ap_Menu_LabelSet.cpp all the different language menu definitons are
included in one large structure. (line 77) then the apropriate language
structure is chosen from them. The upshot of this is if there are
problems compiling a language that you don't use, you still can't compile.
I solved this for my own testing purposes by commenting out all the
languages except EnUS in ap_Menu_LabelSet_Languages.h However, this is
obviously not a solution. However, as I am unable to do the translation
work myself for all these menus, I am not sure what I should do in order
to get it done. Currently, for strings, if one is not defined, we fall
back to english. But for menu items, they all have to be defined for all
the languages we have. If this is inevitable, then I would appreciate
help getting this patch translated in to all the different languages. If
it is not, then what coding needs to be done in this area?
hope this helps clarify my question
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b25 : Thu Feb 10 2000 - 15:46:09 CST