Re: lets merge i18n back into trunk

2005-10-23 Thread Robert Wittams
hugo wrote: > Hi, > > >>Sounds good to me. The new-admin branch probably still does have a few >>issues ( hard to test everything with this many changes!). There are >>also just a couple of API issues (extra methods to be exposed on the >>manipulator). > > > I plan to use your new_admin branch

Re: lets merge i18n back into trunk

2005-10-23 Thread hugo
>here's the .po file. In SVN now. bye, Georg

Re[2]: lets merge i18n back into trunk

2005-10-23 Thread Radek
Hi, here's the .po file. Radek 23. øíjna 2005, 23:16:47, napsal jste: > Hi! >>Here is the patch for czech translation. > Please send translation files as full .po files - they aren't that big. > Applying patches sometimes produces problems (like with your patch - > don't know why exactly, bu

Re: lets merge i18n back into trunk

2005-10-23 Thread hugo
Hi! >Here is the patch for czech translation. Please send translation files as full .po files - they aren't that big. Applying patches sometimes produces problems (like with your patch - don't know why exactly, but it just runs wild when applying) and it's allways easier to just copy the transla

Re: lets merge i18n back into trunk

2005-10-23 Thread hugo
Hi, >Sounds good to me. The new-admin branch probably still does have a few >issues ( hard to test everything with this many changes!). There are >also just a couple of API issues (extra methods to be exposed on the >manipulator). I plan to use your new_admin branch for my CMS thingy as soon as

Re: lets merge i18n back into trunk

2005-10-23 Thread Robert Wittams
hugo wrote: > Hi, > > I think the i18n branch is ready for merging into trunk. I am using it > on two apps (my gallery and my cms project) and it looks quite good to > me. I first thought about adding some more translation hooks to the > admin before merge, but I think that should wait: rjwittams

Re: lets merge i18n back into trunk

2005-10-23 Thread hugo
>I'll get back to the list today or tomorrow with any comments I have >on the i18n branch; thanks again! Ok, then I will refrain from any functional chanages to the branch and only do translation updates, so that you have something functionally stable to check and not a "moving target" to hunt ar

Re: lets merge i18n back into trunk

2005-10-23 Thread Jacob Kaplan-Moss
hugo -- I like your plan of attack, and svn switching to the i18n branch didn't cause any headaches for me, so likely we're good to go. I'd like to take some time to review the branch and see if there's anything we should discuss, but at first glance I'm blown away by how awesome this i

Re: lets merge i18n back into trunk

2005-10-23 Thread hugo
Hi, >There are other parts that the i18n branch deliberately doesn't >address, like date formats and other l10n stuff. at least for date formats I added a sample on how it can be done. The idea is to define technical message IDs for formats and to add the language-specific date formats as transl

lets merge i18n back into trunk

2005-10-23 Thread hugo
Hi, I think the i18n branch is ready for merging into trunk. I am using it on two apps (my gallery and my cms project) and it looks quite good to me. I first thought about adding some more translation hooks to the admin before merge, but I think that should wait: rjwittams says his new_admin bran