I'm not particularly fond of having the entire manual in that directory (images and all). If we're committed to distributing the manual with every Habari release, I'd say its translatable strings should be lumped in with core software's (for easiest management) before they're shipped off to Launchpad to handle translation - basically treat it as if it were another physical page of the admin. The downside there would be that it's "packaged" with the release - but of course that wouldn't matter if we're going to distribute it with the release anyway. This would be made even easier if we actually dumped the manual into the main repository, rather than having its own git repo. In that case, I believe the script that generates the .pot would "just work" with it if we wrapped up the strings, though we'd have to integrate translations back into the manual in some more sophisticated fashion than "and here's a copy in Canuck". -----Original Message----- From: "Matt Read" <[email protected]> Sent: Friday, August 31, 2012 3:18pm To: [email protected], [email protected] Subject: [habari-dev] Locales
each locale from Launchpad is now available as a git repo at https://github.com/habari-locales I'm still wondering how best to facilitate the translation of the manual. currently my idea is to include it in the git locale repo as in https://github.com/Habari-Locales/en_CA/tree/master/dist/doc So anyone with any ideas please speak up :) -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
