15:03:10 RRSAgent has joined #alreq 15:03:10 logging to http://www.w3.org/2016/06/28-alreq-irc 15:03:13 present+ 15:03:15 present+ 15:03:59 Shervin has changed the topic to: ALReq Weekly Meeting, 28 June 2016: Agenda and Details 15:04:09 ScribeNick: mostafa 15:04:19 Chair: Shervin 15:04:30 present+ 15:05:15 agenda+ Reviewing “2.3 direction” draft[2]. Mostafa will have an initial 15:05:32 agenda+ Discussing drafting start of the justification section 15:05:43 agenda+ Status review of action items 15:05:55 agenda+ Review of Github issues [4] and pull requests 15:06:53 https://github.com/w3c/alreq/wiki/Draft-for-%E2%80%9C2.3-Direction%E2%80%9D 15:07:03 Shervin: In the wiki page for the “2.3 direction’ draft I’m seeing this draft. 15:09:02 Mostafa: I didn’t go into fine details and edge cases in this draft. 15:11:15 … It’s just a big picture overview of how the Arabic text is rendered. 15:14:19 http://unicode.org/cldr/utility/bidi.jsp?a=%DA%A9%D9%84%D9%85%D9%87+word&p=Auto 15:14:31 Richard: The image for the logical/visual order can be a little confusing. 15:15:06 … An arrow could help. 15:15:22 Shervin: Another option is to add position numbers. 15:17:51 s/Heh/Teh/ 15:18:11 s/U+0647/U+0629/ 15:21:25 Richard: We can use “display order” instead of “visual order” to make it more clear. 15:21:58 Shervin: We can also use something like “memory order” for “logical order”. 15:22:14 … Or “reordered string” instead of “visual order”. 15:24:12 q+ 15:28:11 ack r12a 15:30:17 … So, do you want me to merge this PR? 15:31:14 Mostafa: No, I have to update this using your feedbacks. 15:31:23 http://quod.lib.umich.edu/j/jep/3336451.0013.105?rgn=main;view=fulltext 15:31:53 Shervin: On the justification, there are two schools of thought. 15:32:21 … One is discussed in the article “Justify Just or Just Jusify”. 15:32:41 … The other is writen about by Thomas Milo. 15:34:52 Richard: Azzedine’s approach is based on adding more kashida. 15:35:07 … Tom’s approach also uses extra spaces between words and inside words. 15:35:55 Shervin: In reality there should be a mix of kashida and inter-word spaces. 15:36:33 Najib: Kashida and inter-word spaces are the main justification mechanisms used in type-writers. 15:37:07 … Justification using ligatures is more complicated and not easy to achieve using mechanics. 15:38:13 Richard: In InDesign they do allow you to use ligatures and swash kaafs in the end of the words, which is not actually kashida. 15:38:41 … Tom’s application, Tasmeem, is used in InDesign. 15:39:06 … But he also thinks that you have to use more spaces than what Azzedine suggests. 15:39:54 q+ 15:39:56 … In type-writers a tatweel is used, not a kashida. They are different. 15:40:54 … These are the tools used for streching the lines for justification. 15:41:09 … And there are the rules for each writing style and each tool. 15:41:39 Shervin: I agree that it’s not black or white. 15:42:41 … It’s also totally dependant on the environment. 15:42:56 … More complex environments can have, for example, longer kaaf. 15:43:10 q+ 15:43:23 Shervin- 15:43:40 q- 15:43:52 ack mostafa 15:44:30 … Plain text environments are more limited and can probably only use tatweels and extra spaces. 15:44:44 … We just have to cover the nuances of using these models. 15:45:49 Mostafa: We can only cover all these tools and solutions, and mention that there are different approaches to mixing these tools. We don’t have to make a decision ourselve.s 15:45:57 Shervin: +1 15:46:46 Richard: At a later step, we can also cover how browsers implement Arabic justification. 15:47:23 … I suggest to use Tom Milo’s definitions for tatweel and kashida. 15:47:43 … When he says “tatweel”, he means the Unicode character. 15:48:40 … But when he says kashida he means extending the horizontal line of the letters. 15:49:36 Shervin: Behnam calls that elongation. 15:54:43 https://github.com/w3c/alreq/wiki/Arabic-numerals-%281st-Draft%29 15:55:20 … Moving on to Najib’s new text. 15:56:10 Najib: I want to cover different families of numbers, what are their origins, and some of the issues regarding the number families like fonts and keyboards. 15:57:00 Writing and reading numbers, bidi with numbers 15:58:23 Shervin: I suggest avoiding Arabic digits term for the U+0030—U+0039. 15:58:38 … It’s defined in the glossary, we can use that. 16:00:35 q+ 16:01:48 ack mostafa 16:04:05 Najib: I have a concern about pronounciation and how the Arab read their numbers 16:04:06 q+ 16:04:11 … What about Persian? 16:05:02 Shervin: I’m not sure about that section. We are talking about text, not how different languages read their texts. 16:05:12 Richard: +1 16:05:31 ack mostafa 16:07:45 Najib: Action-37 is done. 16:08:00 Mostafa: Action-55 is still ongoing. 16:08:52 rrsagent, draft minutes 16:08:52 I have made the request to generate http://www.w3.org/2016/06/28-alreq-minutes.html r12a 16:08:59 https://github.com/w3c/alreq/blob/gh-pages/misc/scripts/generate-glossary.groovy 16:09:36 rrsagent, make log public 16:09:53 Zakim, please leave us 16:09:53 I don't understand 'please leave us', Shervin 16:10:27 zakim, excuse us 16:10:27 leaving. As of this point the attendees have been r12a, mostafa, Shervin, najib 16:10:27 Zakim has left #alreq 16:10:41 https://www.w3.org/2016/06/21-alreq-minutes.html 16:12:35 najib has left #alreq