Am Freitag, den 08.04.2005, 08:39 -0600 schrieb Brian Paul: > This is basically for I18N, right?
Yes. > > You mention that Python and the gettext tools to run the Makefile. > Will everyone need these? I.e. is there a new dependency here? Python and gettext will be needed to generate a header file that will be used by the drivers. I'm thinking to put the generated header into CVS just like other Python-generated files in Mesa. When options are added or translations updated a new version will have to be generated and committed to CVS. gettext tools will also be needed to update the message catalog and translations from the option template that contains options with English descriptions. Developers who add new options and translators who add a new language will need to do this. People who just want to build Mesa/DRI don't need any additional software. My only concern is if you can live with another deeper subdirectory in Mesa or if you'd like it somewhere else up the tree hierarchy. Either way, I'd recommend putting all the I18N stuff for option descriptions in a separate subdirectory because it will accumulate more files for new languages and because the process that generates the option header creates further temporary files and even subdirectories for each language. I'd like to keep these out of the way. Regards, Felix > > -Brian > > > Felix Kühling wrote: > > I haven't got any feedback on this yet. I have made a few improvements > > and as far as I'm concerned it's ready for CVS. If no one objects I'll > > commit this over the weekend. I'll also update the documentation in the > > Wiki about adding new options and translations. > > > > Regards, > > Felix > > > > Am Dienstag, den 29.03.2005, 02:19 +0200 schrieb Felix Kühling: > > > >>Hi, > >> > >>[ For the proposal outlined below I would like to create a new directory > >>in Mesa CVS. Brian, is this ok with you? What about > >>mesa/src/mesa/drivers/dri/common/xmlpool? Any objections or > >>alternatives? ] > >> > >>I thought about how translatability of driver options could be improved. > >>My recent experience with using gettext in DRIconf got me thinking if > >>the same tools could be used for translating driver options. > >> > >>This would have two big advantages: > >> > >> 1. Gettext and related tools are well known to translators, even > >> without programming experience. > >> 2. Translations for different languages are maintained in separate > >> files, which also makes life easier for translators. > >> > >>However, then a mechanism is needed to combine all the translations into > >>a single file, because the XML schema that drivers use to advertise > >>their options wants all translations of an option in one place. > >> > >>I have written a small Python script that does the job of generating > >>something like xmlpool.h (options.h) from a template file (t_options.h) > >>containing the English descriptions and gettext translations in separate > >>files. > >> > >>I'll be offline for the rest of the week. Therefore I'm attaching > >>a .tar.gz containing the work I have done so far for interested people > >>to look at. It contains a new common/xmlpool.h and a directory > >>common/xmlpool with the option template t_options.h, a German > >>translation de.po, and everything that's needed for maintaining > >>translations and generating options.h from t_options.h+translations. > >> > >>This is already working for me. To try this live, extract the tarball in > >>mesa/src/mesa/drivers/dri. Then cd into common/xmlpool and run "make" to > >>generate options.h (you need Python and the gettext tools installed). > >>Then rebuild the drivers. Take a look at the start of > >>common/xmlpool/Makefile for details about adding new translations. > >> > >>Regards, > >> Felix > >> > -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
