- From: Khaled Hosny <khaledhosny@eglug.org>
- Date: Wed, 18 Jan 2017 22:57:15 +0200
- To: Behnam Esfahbod <behnam@behnam.es>
- Cc: r12a <ishida@w3.org>, public-i18n-arabic@w3.org
IIRC, they are usually treated as some sort of immutable boxes, so no extra justification unless they were originally justified, some times even the original line breaks are kept. I’ll see if I can find some examples. Regards, Khaled On Wed, Jan 18, 2017 at 12:40:10PM -0800, Behnam Esfahbod wrote: > Interesting point, Khaled. So, in those cases, we should expect "word > space" to be used for justification, if needed, right? Can find published > examples? > > -b > > > On Wed, Jan 18, 2017 at 12:35 PM, Khaled Hosny <khaledhosny@eglug.org> > wrote: > > > On Wed, Jan 18, 2017 at 01:37:03PM +0100, r12a wrote: > > > Mostafa: The whole idea seems strange to me. Because a main > > > goal in justification is to keep the look of the lines similar. > > > ... To avoid too much space or kashida in one place and less in > > > other places. > > > ... This suggestion is against that goal. > > > > > > Najib: Generally, a quote from Quran is set in a different > > > style that the rest of the text. > > > ... And generally they don’t apply justification to that. > > > > > > Behnam: What happens when a quote spans multiple lines, > > > including lines that only include that Quran quote? > > > > I think it is worse noting that a very common way to typeset Quranic > > quotation among Arabic publisher is to use special applications that > > inserts the Quranic verses as inline images or special fonts when each > > word is a single glyph (usually done to replicate the calligraphic style > > of tubular Musahaf, or to overcome the difficulties of properly > > typesetting Quran). So I’d not read much in the lack of justification in > > some of these examples (threeKindJustify.jpg, for example, clearly uses > > one of these methods). > > > > Regards, > > Khaled > > > > > > > -- > Behnam Esfahbod | بهنام اسفهبد > http://behnam.es/ > GPG-FP: 3E7F.B4B6.6F4C.A8AB.9BB9.7520.5701.CA40.259E.0F8B
Received on Wednesday, 18 January 2017 20:57:52 UTC