W3C home > Mailing lists > Public > www-svg@w3.org > October 2008

RE: Comments on SVG Tiny 1.2

From: Richard Ishida <ishida@w3.org>
Date: Fri, 10 Oct 2008 17:22:05 +0100
To: "'Felix Sasaki'" <fsasaki@w3.org>, "'Doug Schepers'" <schepers@w3.org>
Cc: <www-svg@w3.org>, <public-i18n-its-ig@w3.org>
Message-ID: <004801c92af4$57c19120$0744b360$@org>

I'll be sending in some comments on the Text and Fonts chapters in a short while.

RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/


> -----Original Message-----
> From: public-i18n-its-ig-request@w3.org [mailto:public-i18n-its-ig-
> request@w3.org] On Behalf Of Felix Sasaki
> Sent: 10 October 2008 16:45
> To: Doug Schepers
> Cc: www-svg@w3.org; public-i18n-its-ig@w3.org
> Subject: Re: Comments on SVG Tiny 1.2
> 
> Hello Doug, all,
> 
> this is a very late follow up on the ITS Working Group comment on SVG
> Tiny 1.2 . I have worked on my action item to provide a section
> describing the usages of ITS 1.0 in SVG Tiny 1.2. See the attached PDF.
> Please let me know if you agree with this draft or need modifications.
> After we have reached consensus on the text I will make a proposal for a
> modified schema (it shouldn't be to many changes).
> 
> Note that this is currently no official comment by the ITS Interest
> Group, but a personal comment / follow up which I am making to meet your
> last call deadline.
> 
> Regards, Felix.
> 
> 
> Felix Sasaki さんは書きました:
> >
> > Hi Doug, all,
> >
> > thank you very much for this positive feedback. I will create a draft
> > of a subsection of
> > http://www.w3.org/TR/SVGMobile12/i18n.html
> > and a proposal for the modification of the SVG Tiny schema.
> > Do you edit SVG Tiny in (X)HTML or do you have an XML source? Feel
> > free to answer this question offline.
> >
> > Felix
> >
> > Doug Schepers wrote:
> >>
> >> Hi, Felix-
> >>
> >> The SVG WG is happy to work with you on this.  We apologize for the
> >> delay in getting back to you, but we wanted to sufficiently review
> >> the spec.
> >>
> >> We believe that ITS should be available for all 'text content'
> >> elements [1], which in SVG 1.2 Tiny are 'text', 'tspan' and
> >> 'textArea'; for SVG Full, this will include 'textPath' (and possibly
> >> others TBD).  We also agree that it's appropriate for 'title',
> >> 'desc', and sometimes 'metadata'.   An interesting question is
> >> whether it is needed for 'script' elements; in many cases, there are
> >> strings in script that should be translated, but the great majority
> >> of script should not.
> >>
> >> We will provide you with more feedback once you finish the first draft.
> >>
> >> [1]
> >> http://www.w3.org/TR/2005/WD-SVGMobile12-
> 20051207/intro.html#TermTextContentElement
> >>
> >>
> >> Regards-
> >> -Doug Schepers
> >> W3C Team Contact, SVG, CDF, and WebAPI
> >>
> >>
> >> Felix Sasaki wrote (on 2/26/08 6:20 PM):
> >>>
> >>> ACTION-54
> >>>
> >>> Dear SVG Working Group,
> >>>
> >>> these are comments on SVG Tiny 1.2. They propose *non-normative
> >>> changes*
> >>> to SVG Tiny 1.2 and are is sent on behalf of the i18n ITS Working
> >>> Group.
> >>>
> >>> 1) We would like to ask you to add ITS 1.0 local markup to the content
> >>> model of the metadata, text, desc, title and tspan elements. Local ITS
> >>> markup is defined within the ITS 1.0 specification at
> >>> http://www.w3.org/TR/its/#att.local.with-ns.attributes
> >>> the "Best Practices for XML Internationalization" document contains
> >>> many
> >>> examples of the usage of this markup.
> >>> http://www.w3.org/TR/xml-i18n-bp/
> >>>
> >>> 2) We would like you to provide the following ITS global rules file for
> >>> SVG Tiny 1.2:
> >>> <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0"
> >>> xmlns:svg="http://www.w3.org/2000/svg">
> >>> <its:translateRule selector="//svg:svg" translate="no"/>
> >>> <its:translateRule selector="//svg:metadata | //svg:text | //svg:desc |
> >>> //svg:title | //svg:tspan" translate="yes"/>
> >>> </its:rules>
> >>>
> >>> Global ITS markup (the its:rules element) is defined within the ITS 1.0
> >>> specification at
> >>> http://www.w3.org/TR/its/#rules
> >>> The its:translateRule element is defined at
> >>> http://www.w3.org/TR/its/#translateRule
> >>> The its:translateRule elements above mean that the default for all
> >>> elements from the SVG namespace is that they are not translatable
> >>> (first
> >>> its:translateRule), with the exception of 5 elements (second
> >>> its:translateRule).
> >>>
> >>> 3) We propose to add a non-normative section to SVG Tiny 1.2 explaining
> >>> 1). 2), e.g. as part of the appendix
> >>> http://www.w3.org/TR/2006/CR-SVGMobile12-20060810/i18n.html
> >>> We will create an initial version of this section if you agree with the
> >>> comments in general.
> >>>
> >>> The rationale for these comments is that we think the standardized
> >>> markup for internationalization and localization purposes provided by
> >>> ITS 1.0 is useful for the internationalization and localization of SVG
> >>> Tiny 1.2, and users and developers of SVG Tiny applications should be
> >>> made aware of these possibilities within the specification itself.
> >>> Note that the ITS 1.0 markup would not influence SVG specific
> >>> processing,
> >>> following your definitions at
> >>> http://www.w3.org/TR/2006/CR-SVGMobile12-
> 20060810/extend.html#ForeignNamespacesPrivateData
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Felix
> >>>
> >>>
> >>>
> >>
> >
> >
> >
Received on Friday, 10 October 2008 16:22:45 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:40 GMT