Glad to know you're still working on this Jabier, Some comments: Realy Im not sure if "requiredFeatures" and "requiredExtensions" are > useful to handle on Inkscape or maybe is better for use on the XML > editor or raw SVG editing for the moment. > I would say that the requiredFeatures/extensions attributes are not useful. They were not very well defined in the original SVG specs, and are inconsistently implemented in browsers. > In my mind, with language only point of view, I need a object dialog > method to redraw a "switch", and a language -or "switch"- widget to: > * Add multilenguage title and desc > * Switch all "switches" to one lang > * Add lang to a "switch". Global? > * Remove a lang > * Insert selected element to a new "switch" in the default lang. > * Handle more Aria atributes? > When *displaying* content, you only use one language at a time for the whole graphic. So for the user interface, you need a single option to switch between languages. I think it would make the most sense to put it within the "View" menu, to make it clear that you are not changing the document, you are changing the way you look at the document.

For defining the language alternatives, I think for a start it would be easiest to focus on switching individual text elements or individual title/desc elements. Allowing switches to make large scale changes to the graphics and layout would probably cause to much complication.

So the place to start would be the object properties dialog (for title/desc) and the text properties dialog. Things you would need: - A drop-down list to declare the language of the content. - An "Add language" button which inserts another text field & language drop-down - If there are more than one languages, some sort of radio-button option for indicating which one is the default.

The following things would be nice extras, but aren't essential: - Make the language selection a two-part drop down for main language (English, Spanish) versus country code variation (Canadian English vs US English vs UK English vs any English)

- A way to re-order the languages. The browser will use the first language that matches one of the user's preferences, so the order matters.

Not that the way for expressing the default in the XML is different: for title/desc, the first option is default. It will also be used if the browser does not support the new SVG 2 language switching feature (Right now, I don't think any browser supports it!). For <switch>, the last option is the default, and it cannot have a "systemLanguage" attribute (although it should still have a xml:lang attribute). Quick demo of the different syntax. The English version is the default, but if your browser is set to use Spanish or French, you should see the visible text in that language. Let me know if you find a browser that also switches the tooltip! http://fiddle.jshell.net/rzz2ac4g/1/

> By the way, about "switches" in webpages with "systemLanguage" > conditional processing attribute, whats the best way to user based > switch a lang? We need a JS hack? > Yes, currently there would need to be a JS hack to allow the user to see a different language without having to change their browser language settings. You would need to change the DOM to re-order the elements and remove the systemLanguage attribute.

> Now im very bussy whith my payed work but hope can take some time to > this proyect but sure not as dedicated as previously :( > I'm pretty sure everyone understands this!

I played around a little more with my language settings, and got the same result as you. On Chrome, the SVG always uses the language I have set for the interface (e.g., the language used for the browser menus and dialogs) regardless of the order of preferred languages for content. This also probably explains why Chrome wasn't matching any country codes. I have filed a bug report with Chromium: - https://code.google.com/p/chromium/issues/detail?id=490140 In Firefox (and iceweasel), I'm not sure why there is a difference between SVG and HTML. Within SVG, the "allowReorder" attribute (which is not in SVG, but is in SMIL) is really important. Without it, Firefox follows the specs literally and uses the first language option in the document that matches *any* of the users preferred language. Try changing the order of the languages so that "es" is before "en", and see what happens. Here is more about that: - https://bugzilla.mozilla.org/show_bug.cgi?id=936517 However, the "allowReorder" attribute seems to be ignored in HTML. I've filed a bug (& am hoping Robert Longson jumps on it, he's pretty good about fixing these things!): - https://bugzilla.mozilla.org/show_bug.cgi?id=1166753 I will make a note to update the SVG2 specs to be more clear about using user preferences and to include the "allowReorder" attribute. It is all a little disappointing. We can still go ahead with making it work in Inkscape, but we can't rely on it always having a useful result in browsers. A feature that we probably want to have in Inkscape is the ability to export the SVG in a specific language, instead of with switches. That way, the author could have a single multilingual file for editing, but could create files for the web or printing that always display a specific way, without having to worry about browser differences.

If a DocBook processor doesn't support SVG <switch>, the other option would be to generate separate, complete versions of the SVG, and include them as alternate media objects with docbook language switchers. Which is another use case for having an "Export in Language" option for Inkscape.

I also glad to hear you Amelia. I have a boring problem. Think the lenguage settings is take by the list on prefered language list on the browser. On iceweasel this link to a SVG file work ok. http://upload.wikimedia.org/wikipedia/commons/e/e1/SystemLanguage.svg But if put it into a HTML file the switch not work http://fiddle.jshell.net/0okbt4oq/ This happends in your browser? About your mail: El mar, 19-05-2015 a las 13:31 -0600, Amelia Bellamy-Royds escribió: > Glad to know you're still working on this Jabier, > > Some comments: > > Realy Im not sure if "requiredFeatures" and "requiredExtensions" > are > > useful to handle on Inkscape or maybe is better for use on the > > XML > > editor or raw SVG editing for the moment. > > > > I would say that the requiredFeatures/extensions attributes are not > useful. They were not very well defined in the original SVG specs, > and are > inconsistently implemented in browsers. > > > > In my mind, with language only point of view, I need a object > > dialog > > method to redraw a "switch", and a language -or "switch"- widget > > to: > > * Add multilenguage title and desc > > * Switch all "switches" to one lang > > * Add lang to a "switch". Global? > > * Remove a lang > > * Insert selected element to a new "switch" in the > > default lang. > > * Handle more Aria atributes? > > > > When *displaying* content, you only use one language at a time for > the > whole graphic. So for the user interface, you need a single > option to > switch between languages. I think it would make the most sense to > put it > within the "View" menu, to make it clear that you are not changing > the > document, you are changing the way you look at the document. Ok I agree but to me is more useful: View->Language Dialog, not sure if i can add elements to the view menu without restart. > For defining the language alternatives, I think for a start it > would be > easiest to focus on switching individual text elements or > individual > title/desc elements. Allowing switches to make large scale changes > to the > graphics and layout would probably cause to much complication. Not sure, I think we can use only one "group" element for each switch stament > So the place to start would be the object properties dialog (for > title/desc) and the text properties dialog. Things you would need: > > - A drop-down list to declare the language of the content. > - An "Add language" button which inserts another text field & > language > drop-down > - If there are more than one languages, some sort of radio > -button option > for indicating which one is the default. Maybe the default is the original/start content? Because default not have lang > The following things would be nice extras, but aren't essential: > > - Make the language selection a two-part drop down for main > language > (English, Spanish) versus country code variation (Canadian > English vs US > English vs UK English vs any English) Im thinking in a input text widget for free write of each new lang because a systemLanguage can handle multiples langs, also not sure if the lang country code variation has a standar because i usualy see in spain "es-ES" but in iceweasel mark it as "es-es" -and "es" only is not fired so maybe for full compatibility we need a long list of langs for each switch stament > - A way to re-order the languages. The browser will use the > first > language that matches one of the user's preferences, so the > order matters. This is the first text i write. If the browser open a SVG match orderer, if is inluded onto a webpage, no. But this need to be fixed by browsers, anyway reorder it is a option like you say better than nothing. > Not that the way for expressing the default in the XML is > different: for > title/desc, the first option is default. It will also be used if > the > browser does not support the new SVG 2 language switching feature > (Right > now, I don't think any browser supports it!). For <switch>, the > last > option is the default, and it cannot have a "systemLanguage" > attribute > (although it should still have a xml:lang attribute). > > Quick demo of the different syntax. The English version is the > default, > but if your browser is set to use Spanish or French, you should see > the > visible text in that language. Let me know if you find a browser > that also > switches the tooltip! > > http://fiddle.jshell.net/rzz2ac4g/1/ I dont see tooltip also viewing the svg direcly on browser > > > By the way, about "switches" in webpages with "systemLanguage" > > conditional processing attribute, whats the best way to user > > based > > switch a lang? We need a JS hack? > > > > Yes, currently there would need to be a JS hack to allow the user > to see a > different language without having to change their browser language > settings. You would need to change the DOM to re-order the > elements and > remove the systemLanguage attribute. > OK > > > Now im very bussy whith my payed work but hope can take some time > > to > > this proyect but sure not as dedicated as previously :( > > > > I'm pretty sure everyone understands this! :) Regards, Jabier.