SVG 2 review request

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

SVG 2 review request

Nikos Andronikos
Hi all,

In the SVG WG, we have reached the point where we feel we’re ready to go to CR with SVG 2.
To confirm this, I would like to request a review of the current draft [1].

To give an overview of what has changed in SVG 2, please see the following wiki page:
https://github.com/w3c/svgwg/wiki/SVG-2-new-features

There are two areas that I think would be of concern:
* text [2]
* language based selection via switch [3]

I don’t believe there should be any new i18n issues as a result of the changes to these sections.
In SVG 2, we mostly defer to CSS for text layout.
Regarding language selection, this is not new to SVG 2, but we have changed selection slightly based on the SMIL allowReorder behaviour.

If you find issues, please raise them on our Github issue tracker:
https://github.com/w3c/svgwg/issues

Or if you’ve been following along the development of SVG 2 and you think everything is ok, please let us know as well.

Looking forward to hearing from you.
Thanks,
Nikos.

1. https://svgwg.org/svg2-draft/
2. https://svgwg.org/svg2-draft/text.html
3. https://svgwg.org/svg2-draft/struct.html#SwitchElement
The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.
Reply | Threaded
Open this post in threaded view
|

RE: SVG 2 review request

Phillips, Addison-2
Hello Nikos,

Thanks for the note regarding SVG2. I have added your document to our Review Radar [1].

> In the SVG WG, we have reached the point where we feel we’re ready to go
> to CR with SVG 2.

It's usually a Bad Idea to withhold your I18N review until this late in your development process. Issues raised at this point will delay your CR. Do you have a specific schedule or due date for our comments? Please be advised that reviews require at least two weeks, since the WG must review issues in our Thursday (1500UTC) teleconference and time must be provided to actually read your document.

Best regards (for I18N),

Addison

[1] http://w3c.github.io/i18n-activity/radar/

Addison Phillips
Principal SDE, I18N Architect (Amazon)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.




> -----Original Message-----
> From: Nikos Andronikos [mailto:[hidden email]]
> Sent: Monday, August 08, 2016 9:30 PM
> To: [hidden email]
> Cc: www-svg <[hidden email]>
> Subject: SVG 2 review request
>
> Hi all,
>
> In the SVG WG, we have reached the point where we feel we’re ready to go
> to CR with SVG 2.
> To confirm this, I would like to request a review of the current draft [1].
>
> To give an overview of what has changed in SVG 2, please see the following
> wiki page:
> https://github.com/w3c/svgwg/wiki/SVG-2-new-features
>
> There are two areas that I think would be of concern:
> * text [2]
> * language based selection via switch [3]
>
> I don’t believe there should be any new i18n issues as a result of the changes
> to these sections.
> In SVG 2, we mostly defer to CSS for text layout.
> Regarding language selection, this is not new to SVG 2, but we have changed
> selection slightly based on the SMIL allowReorder behaviour.
>
> If you find issues, please raise them on our Github issue tracker:
> https://github.com/w3c/svgwg/issues
>
> Or if you’ve been following along the development of SVG 2 and you think
> everything is ok, please let us know as well.
>
> Looking forward to hearing from you.
> Thanks,
> Nikos.
>
> 1. https://svgwg.org/svg2-draft/
> 2. https://svgwg.org/svg2-draft/text.html
> 3. https://svgwg.org/svg2-draft/struct.html#SwitchElement
> The information contained in this email message and any attachments may
> be confidential and may also be the subject to legal professional privilege. If
> you are not the intended recipient, any use, interference with, disclosure or
> copying of this material is unauthorised and prohibited. If you have received
> this email in error, please immediately advise the sender by return email and
> delete the information from your system.
Reply | Threaded
Open this post in threaded view
|

Re: SVG 2 review request

r12a
On 09/08/2016 16:35, Phillips, Addison wrote:
> Please be advised that reviews require at least two weeks, since the WG must review issues in our Thursday (1500UTC) teleconference and time must be provided to actually read your document.

Btw, to my mind the time crunch really comes if we find something we
believe needs to be changed.  The review itself is usually much less
time-consuming than the  explanations, discussions, tracking, etc that
are involved in addressing issues that arise.

Just wanted to mention that so that it doesn't come as a surprise.

cheers,
ri


Reply | Threaded
Open this post in threaded view
|

Re: SVG 2 review request

Nikos Andronikos

> On 10 Aug 2016, at 4:53 PM, r12a <[hidden email]> wrote:
>
> On 09/08/2016 16:35, Phillips, Addison wrote:
>> Please be advised that reviews require at least two weeks, since the WG must review issues in our Thursday (1500UTC) teleconference and time must be provided to actually read your document.
>
> Btw, to my mind the time crunch really comes if we find something we believe needs to be changed.  The review itself is usually much less time-consuming than the  explanations, discussions, tracking, etc that are involved in addressing issues that arise.
>
> Just wanted to mention that so that it doesn't come as a surprise.
>
> cheers,
> ri
>
>

Thanks, we understand the situation.
Because of our deferral to CSS for any of the new text layout features, I think that any issues that arise specifically on SVG 2 will be minor.

A two week review period is fine.

Cheers,
Nikos.



The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.