- From: Aharon (Vladimir) Lanin <aharon@google.com>
- Date: Mon, 16 Apr 2012 20:06:56 +0300
- To: Eric Muller <emuller@adobe.com>
- Cc: public-i18n-bidi@w3.org
- Message-ID: <CA+FsOYa_euhAJ-vd03GAndQyCJzH06WzBLw-x80VXZJ9ufgScg@mail.gmail.com>
> It seems to me that if you want a <pre> wrapping a plain text to behave just like that plain text, you have to unicode-bidi:isolate it. Yes, it does need isolation, by it does not need unicode-bidi:isolate to achieve it, for two reasons: - <pre>, by default, has display:block, and thus forms a separate bidi paragraph. - Even if we forego <pre>, and use <span style="unicode-bidi:plaintext>, we get isolation because the unicode-bidi:plaintext states that on inline elements it gets bidi isolation just like unicode-bidi:isolate (plus the per-paragraph first-strong base direction). Aharon On Tue, Mar 20, 2012 at 6:19 PM, Eric Muller <emuller@adobe.com> wrote: > On 3/19/2012 4:42 PM, fantasai wrote: > >> I used to think that, too. But the problem is that that would be >> inconsistent with the way plaintext works. Right now the end of the >> paragraph is basically infinite PDFs. If we transform a piece of plaintext >> to HTML via <pre>, it should continue to behave the same way; introducing >> smart re-opening would break that. >> > > As it the risk of misinterpreting what you have in mind; either: > > - the <pre> is in its own, and there is nothing to reopen, so reopening is > not a problem > > - the <pre> is under the influence of a unicode-bidi:embed/bidi-**override, > in which case the each paragraph in the <pre> text may be affected by that > unicode-bidi:, so you are in trouble before considering reopening. > > It seems to me that if you want a <pre> wrapping a plain text to behave > just like that plain text, you have to unicode-bidi:isolate it. > > Eric. > > >
Received on Monday, 16 April 2012 17:07:49 UTC