launchpad help|
Size: 1538
Comment:
|
Size: 1834
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''Important:''' this page is in preparation for the release of feature that is not yet available in Launchpad. ~-[[FrontPage|Launchpad Help]] > [[Translations]] > Partial PO file exports -~ |
|
| Line 2: | Line 6: |
| Many translation files hosted at Launchpad.net have been imported from an upstream project. For various reasons these imported translations may be changed through the Launchpad.net web interface. In most cases these changes should be provided back to the upstream project to give them a chance to incorporate them into project's original translations. Launchpad.net helps with this by providing the possibility to export only those strings from a PO file that have been changed. | |
| Line 4: | Line 7: |
| == How to request the export == | Distributions, such as Ubuntu, use Launchpad to translate the free software packages that make up the operating system. Where an upstream project has an existing translation effort, the distribution's translators can import the upstream PO files into Launchpad and either customise those translations to the distro's needs or make further translations. To make it easier for upstream projects to take advantage of this translation work, Launchpad can generate a partial PO file that contains only the translations made since the last import of upstream translation files. == Requesting a partial export == |
| Line 8: | Line 18: |
| Full PO files contain full gettext header information about the file. They can be edited offline and re-imported into Launchpad.net using the upload facility. | |
| Line 10: | Line 19: |
| Partial PO files do not contain the usual gettext header but only a warning about their nature. They cannot be re-imported into Launchpad.net because the import validation will reject them due to the missing header. Please use these files ''only'' to merge the translation strings into existing full PO files at the upstream project which then in turn may and should be imported into Launchpad.net again. | While a standard PO file has a full gettext header, and so can be edited offline and then re-imported into Launchpad, the partial PO files that Launchpad provides do not have a header. '''Note:''' partial PO files cannot be re-imported into Launchpad because their lack of a header makes them fail the import validation. Please use these files only to merge the translation strings into existing full PO files. Those merged PO files can then, of course, be imported into Launchpad. ||<tablestyle="width: 100%;"> ~-[[Translations|< Translations]] -~ || |
Important: this page is in preparation for the release of feature that is not yet available in Launchpad.
Launchpad Help > Translations > Partial PO file exports
Exporting partial gettext PO files
Distributions, such as Ubuntu, use Launchpad to translate the free software packages that make up the operating system. Where an upstream project has an existing translation effort, the distribution's translators can import the upstream PO files into Launchpad and either customise those translations to the distro's needs or make further translations.
To make it easier for upstream projects to take advantage of this translation work, Launchpad can generate a partial PO file that contains only the translations made since the last import of upstream translation files.
Requesting a partial export
When you are on the web page for the PO file in question, select "Download" from the grey menu bar. You will be presented with the option to choose the file format for the download - either MO or PO format. If you choose the PO format, you will have the choice to either export the full file or just those strings that were changed since they were imported.
How partial PO files differ from full PO files
While a standard PO file has a full gettext header, and so can be edited offline and then re-imported into Launchpad, the partial PO files that Launchpad provides do not have a header.
Note: partial PO files cannot be re-imported into Launchpad because their lack of a header makes them fail the import validation. Please use these files only to merge the translation strings into existing full PO files. Those merged PO files can then, of course, be imported into Launchpad.
