On Apr 6, 2006, at 10:39 PM, Andrius Ramanauskas wrote:
Hi,
I am currently planning to add support for internationalized (translatable) SVG documents. And I guess it is better to share my thoughts before going deep to implementation, so everyone will be aware of my plans and maybe someone will criticize or adjust my plans. My current plan is to implement this in steps:
- 1 step - <switch> support. I already tested prototype of semi-
working switch element support, but there still some work to do. Currently switch element works just like <g>, but I will make it work according to SVG standard - to render only first element which conditional properties evaluate to true (I will implement support for "systemLanguage" property for a start, which will evaluate to true if property is not set or contains current document language). I plan to make SPSwitch a subclass of SPGroup, so user can enter switch element (turn it into a temporery layer, which will show all contained items, not just first)
See if you can track down any info on proposed changes to <switch> for SVG 1.2. I believe there was possibly quite a bit in there. I seem to recall something about it applying to more areas...
It would be good if whatever you coded at least could leave room for extending to 1.2 as needed.
You also might want to look at more than just language as you do that. One thing we want to be able to do is support different "target" platforms... SVG Tiny, specific browsers, Phones, PDA's, etc... so their impact on <switch> would be something to at least keep in mind.