| Summary: | Internationalize polkit? | ||
|---|---|---|---|
| Product: | PolicyKit | Reporter: | Miloslav Trmac <mitr> |
| Component: | libpolkit | Assignee: | David Zeuthen (not reading bugmail) <zeuthen> |
| Status: | RESOLVED MOVED | QA Contact: | David Zeuthen (not reading bugmail) <zeuthen> |
| Severity: | normal | ||
| Priority: | medium | CC: | piotrdrag |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | 0001-Always-distribute-polkit-1.pot-for-translators.patch | ||
|
Description
Miloslav Trmac
2013-05-13 15:51:04 UTC
Created attachment 80296 [details] [review] 0001-Always-distribute-polkit-1.pot-for-translators.patch If we do internationale polkit... RFC: Should we ship the .pot file? IIRC intltool-using projects usually don't, and rely on (intltool-update) instead. I would prefer that we use Transifex for this. I've been meaning to set that up for a long time now. See the udisks repo for how it's used, specifically http://cgit.freedesktop.org/udisks/tree/.tx/config https://www.transifex.com/projects/p/udisks/ Right, I forgot to mention that the choice of including .pot in the repo or not depends on the translation mechanism; transifex does require a .pot on a public URL (which is easiest to do in the repo). Anyway, the .pot issue is trivial compared to the rest of the work required to i18n and set up the translation architecture. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/polkit/polkit/issues/13. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.