#21 — user interface not translated
by
Harald Friessnegger
—
last modified
Jul 29, 2010 08:32 AM
| State | Tested and confirmed closed |
|---|---|
| Version: | 0.8.2b2 |
| Area | User interface |
| Issue type | Bug |
| Severity | Low |
| Submitted by | Harald Friessnegger |
| Submitted on | Mar 08, 2010 |
| Responsible | Nathan Van Gheem |
| Target release: |
—
|
the existing translations do not work on my buildout (plone4.0a5).
zope2.12's pts seems to compile mo files in i18n folders, but not those in locales.
according to the changlog mo files have been removed in 0.7b2.4:
* because translations had .mo files, it broke some systems--removed.
compiling the po files manually and restarting the instance brings back translations.
(msgfmt -o collective.plonetruegallery.mo collective.plonetruegallery.po)
should mo files be added to the package again, or is there another way to make translations work again?
zope2.12's pts seems to compile mo files in i18n folders, but not those in locales.
according to the changlog mo files have been removed in 0.7b2.4:
* because translations had .mo files, it broke some systems--removed.
compiling the po files manually and restarting the instance brings back translations.
(msgfmt -o collective.plonetruegallery.mo collective.plonetruegallery.po)
should mo files be added to the package again, or is there another way to make translations work again?
- Steps to reproduce:
- install truegallery
set language to german (or some other language there should be a translation for)
make a folder a gallery and go to folder/@@gallery-settings
Added by
Nathan Van Gheem
on
Mar 08, 2010 02:14 PM
I'll look into this. This really needs to be fixed before Plone 4 is released.
Issue state:
Unconfirmed
→
Confirmed
Severity:
Medium
→
Important
Responsible manager:
(UNASSIGNED)
→
vangheem
Added by
Nathan Van Gheem
on
Mar 10, 2010 05:50 AM
This is fixed in the svn. Will cut a release soon.
Issue state:
Confirmed
→
Resolved
Added by
Harald Friessnegger
on
Mar 10, 2010 09:49 AM
translations show up again.
Issue state:
Resolved
→
Tested and confirmed closed
just curious about moving everything into i18n/ and drop the locales/ folder:
i thought the locales folder is the way to go and i18n is just used to be able to add additional translations to the plone domain?
did you speak to someone from the i18n team about what's the best practice for that?
Added by
Nathan Van Gheem
on
Mar 10, 2010 01:06 PM
It was an oversight on my part with little sleep and just trying to get things taken care of. I was referring to another product while fixing some other things with the a few of the translations and it turns out that I went and did the wrong this for the i18n directory. I'm reverting the changes now and making another release.I got an email from someone else saying that it broke their setup this way(not sure why it'd do that)..
Added by
Harald Friessnegger
on
Mar 15, 2010 03:08 PM
i can confirm that b3 contains broken po files that prevent my zope instance from starting up.
Issue state:
Tested and confirmed closed
→
Confirmed
the error occures when placelesstranslationservice is trying to compile the hidden po files that might have been checked in accidentally.
removing ._collective.plonetruegallery-*.po fixes the problem.
we should release a new version that fixes this asap.
Added by
Nathan Van Gheem
on
Mar 16, 2010 01:29 AM
Thank you for looking into this. Due to circumstances, it looks like I won't be able to make a release until tomorrow. If you can't wait, I could give you access to make the release too.
Added by
Nathan Van Gheem
on
Mar 16, 2010 10:11 AM
new release fixes this. Sorry for the trouble.
Issue state:
Confirmed
→
Resolved
Added by
Harald Friessnegger
on
Mar 16, 2010 11:03 AM
the 0.8.2b4 update fixed the problem, thx. however, the question of 2010-03-10 is not yet answered:
Issue state:
Resolved
→
Confirmed
according to the developer manual the i18n folder should not be used for new packages. (http://plone.org/[…]/introduction)
do we stick with the i18n folder since it's more convenient not having to compile updated po files?
alternatively we use the locales folder and add an i18n.sh script that extracts new ids, syncs them to all po files and compiles existing po files automatically.
(eg http://dev.plone.org/[…]/i18n.sh)
Added by
Nathan Van Gheem
on
Mar 16, 2010 11:15 AM
You're right; however, I was not able to get it to work with the locales folder. Maybe something has changed? I'm really sorry I can't put more effort into looking more into this and doing this "right", but for now I need to do what works because I just don't have the time.
Added by
Harald Friessnegger
on
Mar 16, 2010 11:29 AM
fine, so let's leave this issue open as a feature-request with a low priority.
Added by
Nathan Van Gheem
on
Mar 31, 2010 11:13 AM
Severity:
Important
→
Low
Added by
Harald Friessnegger
on
Jul 28, 2010 01:28 PM
i moved the translation files back into the locales folder and added a script (collective/plonetruegallery/i18n.sh) to rebuild pot, sync to po files and compile mo files.we need to decide whether we check in mo files (which i personally do in my projects, since i release from svn tags using jarn.mkrelease) or we do not add them to the svn repository but make sure to compile them before doing a release (which is what they do for tinymce, see http://dev.plone.org/plone/ticket/10666)
Added by
Nathan Van Gheem
on
Jul 28, 2010 01:34 PM
I will do whatever you suggest as I do not understand translations well enough to make an informed decision about it.So basically, whenever a translation changes, we'd just run i18n.sh and commit anything changed or new?
Added by
Harald Friessnegger
on
Jul 28, 2010 03:04 PM
if you add a new msgid run i18n.sh to update the pot file and sync the new msgid to the po files of all languages.when you edited a po file of a language (preferably using poedit or some other tool) run i18n.sh to (re)compile the corresponding mo file.
when releasing the package you need to make sure to include the mo files otherwhise all messageids stay untranslated.
it depends on the tools you use for doing a release whether you'd want to check in mo files or not.
my suggestion is to check them in (this way you can't forget to check them in and people using the package as development egg get translations too), although some other people would tell you not to do it.
Added by
Nathan Van Gheem
on
Jul 29, 2010 08:22 AM
Issue state:
Confirmed
→
Resolved
Added by
Harald Friessnegger
on
Jul 29, 2010 08:32 AM
jarn.mkrelease releases mo files too even though they are not added (maybe it will skip them as soon as we add them to svn:ignores) in the meantime it works w/o checking in mo files
Issue state:
Resolved
→
Tested and confirmed closed
No responses can be added.
If you can, please log in before submitting a reaction.