El mar, 26-08-2003 a las 11:43, Christian Rose escribió: > tis 2003-08-26 klockan 05.07 skrev Shaun McCance: > > > > Because of that, this would still constitute a string freeze break. > > > > > > > > Of course, it would be great if this procedure was followed for the > > > > 2.4.1 release, because the entire idea of intltools was to put every > > > > string that needs translation into the PO file (including XML files). > > > > > > > > Actually, I believe that entire XSLT stylesheet should be made to use > > > > intltools (make it a style.xml.in, and preprocess it while building/ > > > > compiling the package -- just like every other package does for schemas > > > > and stuff). If nobody disagrees, I'll file this as a bug with bugzilla. > > > > > > All right, this is not going to work unless somebody knows how to do > > > stuff that I don't. So far as I can tell, intltool's XML methods just > > > make multiple elements, each with an xml:lang attribute. This is a > > > perfectly reasonable thing to do. Unfortunately, it's not the format > > > used by gentext, the system in place in the stylesheets. > > > > > > Please note that I did not create gentext, and the decision to use it is > > > not arbitrary. It's a part of Norm Walsh's stylesheets, which Yelp > > > builds off of. Transitioning away from gentext would involve creating > > > stylesheets that implement the same API, sticking them inside of the > > > nwalsh xsl directory, and mapping them onto another system. That is a > > > lot of work. It also further ties Yelp to its shipped copies of the > > > nwalsh xsl, making it more difficult to use from other systems. It also > > > means we lose translations made upstream. > > > > I take this back. I've managed to override gentext fairly easily with a > > system that pulls translations from a file that's very intltoolable. Is > > this something the translation team would like me to do? I would do > > this on cvs HEAD after branching for 2.4, but it could be merged into > > 2.4.1 if there aren't any problems. > > > > Doing this will introduce 50-100 strings into the po files. But at that > > point, all translations in Yelp would be handled with intltool. > > This sounds excellent and much needed, but please do this on HEAD only > after branching for 2.4 -- it's way too late to add that many strings in > 2.4.x. Definately 2.5.x material IMHO. > Other than that, a big thanks for looking into this! I don't think it should wait until 2.5.x releases, it's a bug that should be fixed not a new feature... Of course, it should be fixed post 2.4.0. Cheers. > > > Christian > > _______________________________________________ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://lists.gnome.org/mailman/listinfo/gnome-i18n -- Carlos Perelló Marín Debian GNU/Linux Sid (PowerPC) Linux Registered User #121232 mailto:carlos@pemas.net || mailto:carlos@gnome.org http://carlos.pemas.net Valencia - Spain
Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmadadigitalmente