I've always expected block-level constructs to
insulate neutral characters from strongly-directioned adjacent characters.

In my class I advise students never to use
<bidi-override direction=""> unless they really
want to mess with Unicode's built-in direction
strength, as every case I can think of
<bidi-override unicode-bidi="embed"> is
sufficient for insulation at the inline-level.

It appears insufficient in Michael's example,
however, and so I have been stymied by his question.

Content-Transfer-Encoding: 8bit

On 03/05/2016 13:21, Tony Graham tgraham@xxxxxxxxxxxxx wrote:
...

----- Oorspronkelijk bericht -----
Van: "Michael M|ller-Hillebrand mmh@xxxxxxxxx"
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>

...

<fo:block>Brand name (Former name)</fo:block>

This is visually rendered like this:

(Brand name (Former name

...

My first idea is to add <fo:bidi-override direction="ltr"> to each
block or maybe only each text node that consist of solely non-Arabic
characters. I guess this could be done using a regular expression like

That will 'un-mirror' the ')' but not change its position. See FO below.

Sorry, yes, 'direction' should apply only to fo:bidi-override. I'll have
to look into what it was doing to fo:block. This will work:

<fo:block><fo:bidi-override
direction="ltr">Brand name (Former name)</fo:bidi-override></fo:block>

Regards,

Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.
----
Skerries, Ireland
tgraham@xxxxxxxxxxxxx

--
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training @US$45: http://goo.gl/Dd9qBK |
Crane Softwrights Ltd. _ _ _ _ _ _ http://www.CraneSoftwrights.com/s/ |
G Ken Holman _ _ _ _ _ _ _ _ _ _ mailto:gkholman@xxxxxxxxxxxxxxxxxxxx |
Google+ blog _ _ _ _ _ http://plus.google.com/+GKenHolman-Crane/posts |
Legal business disclaimers: _ _ http://www.CraneSoftwrights.com/legal |

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus