RE: New article draft for review: Working with source code markup and code examples for RTL scripts

… and having said that, now I see where you do call it out several times. 

 

From: Addison Phillips <addisoni18n@gmail.com> 
Sent: Thursday, April 6, 2023 12:14 PM
To: 'r12a' <ishida@w3.org>; 'Internationalization Working Group' <public-i18n-core@w3.org>
Subject: RE: New article draft for review: Working with source code markup and code examples for RTL scripts

 

Hi Richard,

 

Thanks for this. The article is really well written.

 

I didn’t see you call out the shaping of the < and > characters. Did I miss it? The shaping aspect means that it is possible to create markup that has apparently unbalanced angle brackets (when in fact they are balanced) as in the screen shot below (the space before em is because the bidi demo page would turn the angle brackets into an emphasis tag otherwise):

 



 

(https://w3c.github.io/i18n-discuss/explainers/bidi-html-demo.html?text=\u0627\u0644\u0628\u062d\u0631\u064a\u0646%20abc%20%3C%20em%20title=\u0645\u0645%3E%20zyx%20\u0627\u0644\u0643\u0648\u064a\u062a!)

 

Also, (putting on my Unicode MFv2 hat for a second), I note that message format placeholders have significant issues in this area. Existing MF and MFv2 use { and } as delimiters and tend to have ASCII tokens inside the placeholders, so this is a consideration for other markup regimes beyond just HTML.

 

Addison

 

Addison Phillips

Chair (W3C I18N WG, Unicode MFWG)

 

Internationalization is not a feature.

It is an architecture.

 

 

 

 

From: r12a <ishida@w3.org <mailto:ishida@w3.org> > 
Sent: Thursday, April 6, 2023 4:53 AM
To: Internationalization Working Group <public-i18n-core@w3.org <mailto:public-i18n-core@w3.org> >
Subject: New article draft for review: Working with source code markup and code examples for RTL scripts

 

While working on the new version of https://w3c.github.io/i18n-drafts/questions/qa-bidi-unicode-controls.en.html (PR at https://deploy-preview-449--i18n-drafts.netlify.app/questions/qa-bidi-unicode-controls.en) we came across a link to https://www.w3.org/TR/2014/NOTE-i18n-html-tech-bidi-20140603/#bidisource, which talks about problems when working on bidi source code.  That page is out of date and no longer used, so i tried to capture the relevant information in a new article.

See https://w3c.github.io/i18n-drafts/questions/qa-bidi-source.en.html for an initial draft.

Any comments?

ri