True, there are advantages and disadvantages to each approach. Esperanto being
the best solution.
For text labels with fields, menu's, navigation etc. I use this. For large
pieces of content, when opening e.g. a blog view with a lot of text, I may
create two views, one with each language. You may be surprised though, if you
design light pages with a lot of pass-through html, how small the downloaded
pages stay.
Advantages of CSS approach:
- less calculations on the server
- less extra fields required
- easier to maintain in designer, as you can see the pass through html on your
forms, instead of being hidden in a computed value
Mark,
True, there are advantages and disadvantages to each approach. Esperanto being the best solution.
For text labels with fields, menu's, navigation etc. I use this. For large pieces of content, when opening e.g. a blog view with a lot of text, I may create two views, one with each language. You may be surprised though, if you design light pages with a lot of pass-through html, how small the downloaded pages stay.
Advantages of CSS approach: - less calculations on the server - less extra fields required - easier to maintain in designer, as you can see the pass through html on your forms, instead of being hidden in a computed value