I fully agree Julian. We are going to have an IRC meeting on Thursday 4 at 17:00 UTC / 19:00 UTC+2 (Barcelona) / 1pm EST at #globalize over on freenode.net to discuss the API. (at least 3 l10n rails plugin teams will try to find a compromise to provide Rails with an awesome localization API)
Feel free to join us. -Matt On Oct 3, 6:05 pm, Julian Tarkhanov <[EMAIL PROTECTED]> wrote: > On 3-okt-2007, at 4:13, Matt Aimonetti wrote: > > > Let's say we use English strings as base for localization and out > > string looks like: 'There were problems with the following fields:'. > > The string itself becomes the translation key or translation reference > > if you will. Each language will use this string as reference. The > > obvious problem occurs when the English is modified. If the string > > becomes: 'There were problems with the following fields' or "A problem > > occurred with the following fields:'then all the translations are > > broken. > > I tried this approach and if you do semi-decent copywriting for your > mesagges and views the keys in the string resources get obsolete > on each commit. I found it to be pretty disastrous. > -- > Julian 'Julik' Tarkhanov > please send all personal mail to > me at julik.nl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
