Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drafting “direction” #28

Closed
mostafah opened this issue Jan 19, 2016 · 13 comments
Closed

Drafting “direction” #28

mostafah opened this issue Jan 19, 2016 · 13 comments

Comments

@mostafah
Copy link
Contributor

I have a draft here in Google Drive. This is very short, because the role of this section is to introduce the direction of the Arabic script briefly and introduce references for further reading and I couldn’t think of more information to put here. If you have any suggestions for what can be added here, please leave a comment.

@r12a
Copy link
Contributor

r12a commented Mar 18, 2016

i think we should move this into the main document. (I added some text to the Google doc which you can accept or delete.)

@mostafah
Copy link
Contributor Author

Sorry if you wanted to expand on this and waited too long. Sent the PR: #40.

@r12a
Copy link
Contributor

r12a commented Apr 19, 2016

To be done: a simple overview of the bidi algorithm.

@r12a
Copy link
Contributor

r12a commented May 17, 2016

Here's a link to the existing description:
https://www.w3.org/International/articles/inline-bidi-markup/uba-basics

@mostafah
Copy link
Contributor Author

I finished the text, but the images are not done yet. The text is available at the same Google Drive document.

I’ll send a PR after I’ve made the images. You can review the text in the meantime.

@r12a
Copy link
Contributor

r12a commented Jun 21, 2016

@mostafah looks good! I suggested a few trivial editorial edits in the doc.

@mostafah
Copy link
Contributor Author

@r12a Thanks for the review and the speed.

@mostafah
Copy link
Contributor Author

Moved the draft to a wiki page for further discussion.

@mostafah
Copy link
Contributor Author

A few weeks ago we discussed the confusion over “logical order” and “visual order.” I updated that part of the draft with what I hope is a simpler explanation of the concept. The change is in the first image and its two preceding paragraphs.

Is this new version any better? More suggestions?

@ntounsi
Copy link
Contributor

ntounsi commented Jul 12, 2016

Figure 1
s/memroy/memory/

Paragraph before last:
May be mention also weak directional property for numerals.

About logical order, I wonder if it's worth to mention why it is "a pain" to work only in visual order. Problems such as writing the text backwards, line wrapping, explicitly right-align text in paragraphs etc.

@mostafah
Copy link
Contributor Author

Thanks for the catch. Updated the image.

I understand the importance of weak directions, but I’m worried it might make this section even more complicated. I know it will be helpful for some curious readers, but I don’t know whether it will be worth it or not. What’s your opinion on this?

I have the same concern about mentioning why we don’t store text in the visual/display order. I thought about adding a sentence like that myself, but then skipped it assuming few people would have that question.

@ntounsi
Copy link
Contributor

ntounsi commented Jul 12, 2016

I share your worry to keep things simple and not go into the technical details, which can be found in external references.

@r12a
Copy link
Contributor

r12a commented Jul 12, 2016

Editorial suggestion: I think the text in figure 1 "The order of characters in memory" should be the caption, and the text "The order of the same characters when displayed" should also be a caption (which of course, means splitting Figure 1 into two figures). As a general rule, i think we should avoid text in graphics where possible, and it seems possible here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants