W3C

- DRAFT -

ALReq Weekly Meeting, 21 February 2017

21 Feb 2017

See also: IRC log

Attendees

Present
mostafa, najib, behnam, r12a, Shervin
Regrets
Chair
behnam
Scribe
mostafa

Contents


<scribe> ScribeNick: mostafa

Status review of action items

<behnam> https://www.w3.org/International/groups/arabic-layout/track/actions/open?sort=owner

Behnam: Action-84 is done.

<behnam> https://github.com/w3c/alreq/issues/86#issuecomment-279963613

<behnam> close action-84

<trackbot> Closed action-84.

Richard: Re some of the Urdu examples from Khaled in the underline: I’m not sure all of them are underlines.
... They look like normal lines drawn under a title, not necessarily underline.

<najib> I think so

<r12a> https://github.com/w3c/type-samples/issues/16

Richard: In the examply in my link, some lines are underlines and some are not underlines.
... That seems quite common.

<r12a> r12a: seems we may need to also describe a requirement for borders to also skip ink

Mostafa: No update on my action item.

Najib: No update on my action.

<behnam> https://www.w3.org/International/groups/arabic-layout/track/actions/open?sort=owner

Shervin: I don’t have any updates on my action items.

Review of GitHub issues and pull requests

<behnam> Drafting issues: https://github.com/w3c/alreq/issues?q=is%3Aissue+is%3Aopen+label%3Adrafting

<behnam> https://github.com/w3c/alreq/pulls

Richard: We have two pending pull requests.

Mostafa: One of the pull requests is mine (#89
... and it is still ongoing.
... It is not ready for merge.

<behnam> https://github.com/w3c/alreq/pull/83

Shervin: Najib’s PR is blocked by me. I’ll try to deal with it next week.

<behnam> action Shervin to convert glossary to HTML format

<trackbot> Created ACTION-86 - Convert glossary to html format [on Shervin Afshar - due 2017-02-28].

<najib> https://github.com/w3c/alreq/issues/57

<behnam> https://github.com/w3c/alreq/issues/57#issuecomment-280176906

<najib> Right repo? https://github.com/w3c/type-samples/issues/12

Najib: I left a comment on the justification issue about tatweel. Not sure if that is the correct place for it.

Richard: This is the right place for this discussion. The other repo is for examples only, not discussion.
... Also, is it common for softwares to add tatweel for justification?

Mostafa: +1 about the right place for this discussion. Helpful on drafting this section.
... I have seen tatweel beeing used on printed works, but I don’t remember seeing a software that does that for justification.

Behnam: For clarification: tatweel means the Unicode character and kashida means elongating the horizontal lines?

Richard: +1

Behnam: Proper kashida elongation which handles curved lines is implemented in special cases like Quran printing.
... But Microsoft Word or Internet Explorer use a line like tatweel for justification.

Najib: Microsoft Word uses tatweel only for some fonts.
... For other fonts like Amiri uses only spaces.

Mostafa: Does the character that Word adds for justification has variable widths?

Behnam: They use variable widths for this tatweel for kashida.

Mostafa: My question is whether we should categorize this implementation as tatweel, or a very basic form of kashida, or something else.

Behnam: We can add a note about this technical implementation.

Shervin: Softwares don’t add characters like tatweel to the text, they just added at the presentation layer.

Mostafa: My question is whether to catagorize a variable-width tatweel as using method tatweel or using kashida.

Shervin: A definition of tatweel will help with answering these kinds of questions.

Najib: I think we can consider a variable width tatweel as kashida.

<Shervin> http://unicode.org/cldr/utility/character.jsp?a=%D9%80&B1=Show

Najib: I have question: do we have tests to see if tatweel changes string comparisions and matches?

Richard: I don’t know.

Shervin: Unicode character properties for tatweel recommends ignoring it in searches.
... But the catch is that if you manually add tatweel in your text, you might want it to be found as part of the text.

Richard: But if you add tatweel for emphasis you still want to find it.

Shervin: Yes. But I have not tested this. But the short answer according to Unicode is that it is not ignorable.

Behnam: In Iran Nastaliq font adding tatweel is used for using extended shapes for letters.
... But that is a special implementation.

Shervin: I recommend to stay away from calligraphy when talking about justification.
... These behaviors are not standard, can be extremes, …

+1

<r12a> +1

scribe: We can stick to typed, monotype style text for these topics and then consider adding edge cases afterwards.

<najib> +1

<behnam> +1

<r12a> https://cloud.githubusercontent.com/assets/4839211/23173609/a0c28b52-f851-11e6-9816-fb209f7ca869.jpeg

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2017/02/21 17:36:06 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/quire/quite/
Succeeded: s/-q//
Succeeded: s/+q//
Found ScribeNick: mostafa
Inferring Scribes: mostafa
Present: mostafa najib behnam r12a Shervin
Got date from IRC log name: 21 Feb 2017
Guessing minutes URL: http://www.w3.org/2017/02/21-alreq-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]