[minutes] Arabic layout telecon 2016-08-30


text version follows:

Arabic Layout teleconference

30 Aug 2016

    See also: [2]IRC log

       [2] http://www.w3.org/2016/08/30-alreq-irc


           Shervin, Mostafa, r12a, Najib




      * [3]Topics
      * [4]Summary of Action Items
      * [5]Summary of Resolutions

    Shervin: I did some cleanup on the document.
    ... I used HTMLTidy.
    ... Some of the lines were cut at 80 characters, some were
    longer. I made them all the same by wrapping at 80.
    ... I also validated against the W3C validator.

    <Shervin> [6]https://github.com/w3c/alreq/pull/63

       [6] https://github.com/w3c/alreq/pull/63

    Shervin: Some of the attributes for the ReSpec I moved into CSS
    to validate with the Validator.
    ... For example, alink and vlink which raise a deprecation

    Richard: These are not related to ReSpec at all.

    Shervin: Our document is currently valid.
    ... I also added a shell script there that uses HTMTidy to
    clean up the code.
    ... The config can be used, but the consistency is a good

    Richard: The problem is that some people may not use the tidy.

    Shervin: We can say that from now on, every time you change the
    document, you keep the style, and every time you want to make
    big changes to the structure of the document, you can use tidy.

    Richard: And we should use tidy before making other changes.

    Shervin: Absolutely, we should never put tidying and editorial
    changes in a single commit.

    <Shervin> [7]https://shervinafshar.github.io/alreq/

       [7] https://shervinafshar.github.io/alreq/

    Shervin: What do you think about the 80-character line rule?

    Richard: I don’t have a strong opinion on it, even though we
    usually don’t care about line width.

    Mostafa: If that is the case, I guess dropping line width would
    be better, because without that tidying would affect less of
    other people’s work.

    Shervin: Ok. It seems like the consesus is on omitting the line
    width rule.



    Shervin: I’ll resubmit my changes without the line width and we
    can revisit it next week.
    ... This work on HTML cleanup is about action-59.
    ... Question for Richard: should we address warnings of the
    validator as well, or just errors?

    Richard: It depeneds. Do you remember the warnings?

    Shervin: I will record the results of the validator for this.



    Shervin: Jumping to agenda item 4: Findings regarding
    justification behaviour in InDesign.
    ... There are a bunch of screenshots in this link.
    ... There is something in InDesign called “stylistic insersion
    of kashida. It applies kashidas in certain places.
    ... For example, one kashida in every word. Only adds kashida
    after some specific letters, like “seen”.
    ... It would be very good if we could talk about these rules.
    ... I saw that we have two terms defined in the document:
    color, and river.

    <najib> +1 to add terms to the glossary (river color ...)

    Mostafa: I added the definitoin to the text as well to help
    with the readers that may not be familiar with the terms.



    Shervin: With ReSpec you can just refer to the terms from
    inside the document.
    ... Najib, for action-58, you have PR #48 open.

    Najib: Yes, I unified the images and added images from

    Shervin: I prefer separate images to a single one.

    Richard: +1. And we should not have captions inside the images.

    <Shervin> [11]https://github.com/w3c/alreq/pull/64/files

      [11] https://github.com/w3c/alreq/pull/64/files

    Shervin: There are a big number of HTML changes in this PR.
    ... For that purpose and the separation of the images, we
    cannot merge this PR.
    ... It should be resubmitted.

    <r12a> [12]http://r12a.github.io/pickers/persian/

      [12] http://r12a.github.io/pickers/persian/

Summary of Action Items

Summary of Resolutions

    [End of minutes]

Received on Wednesday, 31 August 2016 09:20:36 UTC