Mailinglist Archive: opensuse (4344 mails)
| < Previous | Next > |
Re: [opensuse] YaST Text Translation for Internationalization / Localization
- From: Karl Eichwalder <ke@xxxxxxx>
- Date: 23 Aug 2005 12:04:09 +0200
- Message-id: <sh8xyt0y1y.fsf@xxxxxxxxxxxxxxx>
"dr. strangedub" <doctorstrangedub@xxxxxxxxx> writes:
> As part of a company project we have created a customized version of
> YaST. Now that we have most of our functionality in place, we need to
> provide for internationalization and/or localization of the product.
That's an interesting request. AFAIK, the yast2-devtools package is
meant to provide tools (Makefiles, scripts) for generating POT files.
These are to be renamed to TEXTDOMAIN.LL.po and translated. Then add
the PO files to the yast2-trans packages and hopefully, you are done.
This procedure is untested for quite some time. I have some glue
scripts for merging and creating final translation packages--I'm not
sure whether these scripts would work outside of our repository.
--
Key fingerprint = B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E
> As part of a company project we have created a customized version of
> YaST. Now that we have most of our functionality in place, we need to
> provide for internationalization and/or localization of the product.
That's an interesting request. AFAIK, the yast2-devtools package is
meant to provide tools (Makefiles, scripts) for generating POT files.
These are to be renamed to TEXTDOMAIN.LL.po and translated. Then add
the PO files to the yast2-trans packages and hopefully, you are done.
This procedure is untested for quite some time. I have some glue
scripts for merging and creating final translation packages--I'm not
sure whether these scripts would work outside of our repository.
--
Key fingerprint = B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E
| < Previous | Next > |