RE: [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-416]

2015-03-20 Thread Christiansen, Kenneth R 
We are tracking our issues in GitHub. Maybe it makes sense filling them there 
instead/as well?

We now have a ´lang´ field. I assume that is not enough?

Kenneth

 -Original Message-
 From: Phillips, Addison [mailto:addi...@lab126.com]
 Sent: Thursday, March 19, 2015 6:32 PM
 To: public-webapps@w3.org
 Cc: public-i18n-c...@w3.org
 Subject: [appmanifest] No direction metadata for 'name' (etc.) [I18N-ISSUE-
 416]
 
 From Tracker:
 
 http://www.w3.org/International/track/issues/416
 
 http://www.w3.org/TR/2015/WD-appmanifest-20150212/#name-member
 
 The 'name' manifest member does not provide a means of indicating the
 base direction of the name string. This is equivalent to extracting the 'dir'
 attribute appropriate for the HTML title element's scope and may be
 necessary for correct rendering of bidirectional content.
 
 For example, the author might need to set the base direction explicitly, since
 the Unicode paragraph detection algorithm can be fooled by a paragraph that
 starts with a strong LTR character, but is actually a RTL paragraph (or vice
 versa), eg. نشاط التدويل is how you say 'i18n Activity' in Arabic.
 
 It would be helpful to the author to be able to set the default base direction
 for a whole manifest file to rtl.
 
 Addison Phillips
 Globalization Architect (Amazon Lab126)
 Chair (W3C I18N WG)
 
 Internationalization is not a feature.
 It is an architecture.

RE: I18N comments on Manifest for Web applications

2015-03-20 Thread Christiansen, Kenneth R 
Hi there,

The spec authors use GitHub for issue tracking. I duplicated your issues there: 
https://github.com/w3c/manifest/issues

Thanks for looking into internationalization issues with the current spec.

Cheers,
Kenneth

 -Original Message-
 From: Phillips, Addison [mailto:addi...@lab126.com]
 Sent: Thursday, March 19, 2015 6:20 PM
 To: public-webapps@w3.org
 Cc: public-i18n-c...@w3.org
 Subject: I18N comments on Manifest for Web applications
 
 Hello Webapps,
 
 As previously mentioned, I am about to send you comments from the
 Internationalization Working Group on your document (whose current
 iteration lives at [1]). Because we use Tracker for our comments, I will be
 sending each comment under separate cover. The I18N WG is always happy
 to discuss our comments or ways to address same. Please let me know if you
 prefer to receive comments in a different format (such as Bugzilla) or if you
 need additional information.
 
 If you want to see a summary of our comments, you can find them tracked at
 [2]
 
 Regards (for I18N)
 
 Addison
 
 [1] http://www.w3.org/TR/appmanifest/
 [2] http://www.w3.org/International/track/products/74
 
 Addison Phillips
 Globalization Architect (Amazon Lab126)
 Chair (W3C I18N WG)
 
 Internationalization is not a feature.
 It is an architecture.

RE: I18N comments on Manifest for Web applications

2015-03-20 Thread Christiansen, Kenneth R 
Marcos, Anssi, what do you think?

I would prefer the comments on GitHub as it seems to be a great place for 
interacting with the web community, judging from our success so far.

Kenneth

 -Original Message-
 From: Phillips, Addison [mailto:addi...@lab126.com]
 Sent: Friday, March 20, 2015 4:43 PM
 To: Christiansen, Kenneth R; public-webapps@w3.org
 Cc: public-i18n-c...@w3.org
 Subject: RE: I18N comments on Manifest for Web applications
 
 Hi Kenneth,
 
 Thanks for the reply.
 
 I know you're using GitHub. However, whenever I'm filing/forwarding
 comments on a document on behalf of the Working Group, I always look at
 the SOTD in the document in question to see what instructions the receiving
 WG has. In this case, you have a fairly generic SOTD, which says in part:
 
 --
 This document was published by the Web Applications (WebApps) Working
 Group as a Working Draft. This document is intended to become a W3C
 Recommendation. If you wish to make comments regarding this document,
 please send them to public-webapps@w3.org (subscribe, archives). All
 comments are welcome.
 --
 
 If you prefer to have comments filed to GitHub, perhaps modify your
 instructions?
 
 Thanks!
 
 Addison
 
 Addison Phillips
 Globalization Architect (Amazon Lab126)
 Chair (W3C I18N WG)
 
 Internationalization is not a feature.
 It is an architecture.
 
 
 
  -Original Message-
  From: Christiansen, Kenneth R
  [mailto:kenneth.r.christian...@intel.com]
  Sent: Friday, March 20, 2015 1:15 AM
  To: Phillips, Addison; public-webapps@w3.org
  Cc: public-i18n-c...@w3.org
  Subject: RE: I18N comments on Manifest for Web applications
 
  Hi there,
 
  The spec authors use GitHub for issue tracking. I duplicated your issues
 there:
  https://github.com/w3c/manifest/issues
 
  Thanks for looking into internationalization issues with the current spec.
 
  Cheers,
  Kenneth
 
   -Original Message-
   From: Phillips, Addison [mailto:addi...@lab126.com]
   Sent: Thursday, March 19, 2015 6:20 PM
   To: public-webapps@w3.org
   Cc: public-i18n-c...@w3.org
   Subject: I18N comments on Manifest for Web applications
  
   Hello Webapps,
  
   As previously mentioned, I am about to send you comments from the
   Internationalization Working Group on your document (whose current
   iteration lives at [1]). Because we use Tracker for our comments, I
   will be sending each comment under separate cover. The I18N WG is
   always happy to discuss our comments or ways to address same. Please
   let me know if you prefer to receive comments in a different format
   (such as Bugzilla) or if you need additional information.
  
   If you want to see a summary of our comments, you can find them
   tracked at [2]
  
   Regards (for I18N)
  
   Addison
  
   [1] http://www.w3.org/TR/appmanifest/ [2]
   http://www.w3.org/International/track/products/74
  
   Addison Phillips
   Globalization Architect (Amazon Lab126) Chair (W3C I18N WG)
  
   Internationalization is not a feature.
   It is an architecture.