© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
5466644
demo site
(Get the code!)
It really makes sense when we consider po files from Horizon source codes: e.g., django.po and djangojs.po, but it is difficult to generalize to apply all po files including po files for Horizon release notes and documentation, and also in openstack-manuals different documents use different po files.
It would be nice if we have better approaches on defining the relationship from multiple po files but since there are Horizon and Horizon plugin projects, it seems that such definition would be a challenge.
To Horizon developers, would it be fine if po files are managed AS-IS status? If then, I would like change it into "Won't fix" status.