> I believe we should follow a rule -- generating HTML markup is fine, > generating user-visible strings is not. If we do include them, they > should be generated by the application, or should be easy to override by > the application. > > Please note that I don't believe simply wrapping them all in some sort > of #t() internationalization thing is the solution [1]. > > I realize this is a lot of work and it will break most tests (they > expect full HTML, which I think is an issue as well), but let's set > ground rules and work on it gradually. That way our patches won't > conflict and people that develop non-english sites will have an easier > job.
I believe that the "internationalization thing" is a solution. Done properly it should also address your highly valid criticisms. Give me a few weeks until I can fully implement my i18n vision in cl-i18n and let's return to the topic afterwards. Leslie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
