W3C

- DRAFT -

ALReq Weekly Meeting, 14 February 2017

14 Feb 2017

See also: IRC log

Attendees

Present
scribe, Behnam, Mostafa, r12a, Shervin
Regrets
Chair
Behnam
Scribe
mostafa

Contents


<behnam> Review of GitHub issues and pull requests

<scribe> ScribeNick: mostafa

Sorry. BRB.

<behnam> https://github.com/w3c/csswg-drafts/projects

<r12a> https://github.com/w3c/i18n-activity/projects/1

<behnam> https://github.com/w3c/csswg-drafts/projects/1

<r12a> https://github.com/w3c/i18n-drafts/projects/1

<behnam> action Behnam to set up a github project for drafting pipeline

<trackbot> Created ACTION-85 - Set up a github project for drafting pipeline [on Behnam Esfahbod - due 2017-02-21].

<behnam> https://github.com/w3c/i18n-drafts/projects/1

<behnam> https://github.com/w3c/i18n-activity/projects/1

<Shervin> +1

Title of the document

<Shervin> https://github.com/w3c/alreq/issues/88

Richard: Three different encounters suggesting to me that they thought our document only covers the Arabic language.
... Because of our title.

<r12a> https://github.com/w3c/alreq/issues/88

Shervin: If someone is surprised by finding out that the Arabic script covers other languages too, they can take a look at the abstract or the very beginning of the document and learn that Arabic script can cover more langauges.
... So, my suggestion is that the current title is good enough, but if we absolutely have to do that, my suggestion is the four titles that I wrote in the issue.

Richard: I agree that the title is described in the document and its educational. But the problem is that some people won’t look into the document because they don’t think it includes those languages.
... This is the case that happened when we were discussing the document with those three teams.

Shervin: It’s a tough choice to include the knowledge of the document in the title.
... I don’t think that it adds something positive to the document, but if we can have a better, clearer title, I go with it.
... It might also help to decouple the languages into sperate documents, like Arabic Layout Requirements and Persian Layout Requirements, but I thought that is not our desired option here.

Richard: Yes. Decoupling does not work because we might want to include Urdu and other langauges.

Shervin: Changing “Arabic” to “Arabic Script” might mean that our document is only about the script, not the whole writing system of Arabic, which can include topics like justification.
... But I think it won’t be a problem with our audiences. So I’m fine with that.

Behnam: I agree with the third option.

Mostafa: The third one is fine by me too.

Richard: I can change the title then, because I want to update other pages that refer to our document.

<r12a> Discussed during telecon. All agreed to use third option above, ie.

<r12a> Text Layout Requirements for the Arabic Script

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/14 17:06:51 $

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/the option/our desired option/
Found ScribeNick: mostafa
Inferring Scribes: mostafa
Present: scribe Behnam Mostafa r12a Shervin
Got date from IRC log name: 14 Feb 2017
Guessing minutes URL: http://www.w3.org/2017/02/14-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]