i18n updates and need to review domains in code

[Christopher Johnson]

Hi all,

I started working on updating the i18n files during the sprint this weekend (thanks again to all who sprinted there!). I wanted to let you all know about progress, some doubts, and some suggestions for uniformity in the language domains.

Currently what I worked on is:
1 getpaid (in getpaid.core)
2 plonegetpaid (in PloneGetPaid)
3 plonegetpaid-plone (in PloneGetPaid)

I checked in updates for (1) as it is fine (thanks to help from Hanno and Maurits's blog), but there seems to be some confusion around 2 and 3. The last one was intended for elements of the Plone UI that we are modifying. For example, the items we add to the actions menu and links in the personal bar such as "order history". All elements of the product that only appear on GetPaid pages in the UI were intended for the "plonegetpaid" domain. It seems these got mixed up somewhat, as the plonegetpaid-plone domain should have very few items.

When I updated the i18n files in PloneGetPaid, there were relatively few changes in plonegetpaid domain, but lots in plonegetpaid-plone (109 added). This means:
a. there are going to be several msgid's that need translating in all languages
b. we will need some cleanup of the domains used on the msgids
I noticed the plonegetpaid-plone domain used in the checkout wizard and the address book, on a quick inspection.

If you have worked on code and used the "plonegetpaid-plone" domain in msgids, can you please review to apply the differentiation explained above?

I filed an issue so we can track progress (#226). I have not checked in my updates in PloneGetPaid as I don't want to lose the translations once the item is fixed.

If there are any questions or suggestions, please me know.

Best wishes,

Chris

--
Cofounder and CEO
ifPeople - Innovation for People
www.ifpeople.net
t: 678-608-3408
130 Boulevard NE, #6
Atlanta, GA 30312