Jan Bares wrote:
> thanks for your support. I want to report you yet another problem, today
> with your FO converter. It seems like problem of MS Word 2003 but your
> converter may fix it. I have this sample text in my DocBook:
>
> <ulink
> url="http://somesite?p1=1&Link=1";>http://somesite?p1=1&Link=1</ulink
>
>
> When this is converted to WML, the result is (cutted):
>
> ...
> <w:hlink w:dest="http://somesite?p1=1&Link=1";>
> ...
>
> Word will not load this document because of the "&Link". Word thinks this is
> chararacter entity and expects semicolon after &Link. When I change "&Link"
> to "&Link", it works fine and Word converts it to '&'. This seems like
> bug in Word, just to let you know.
No, for once MS-Word is right... XFC should actually output the ampersand as
a character entity reference. This will be fixed in the next release.
Thanks for reporting this,
--
Jean-Yves Belmonte <john at pixware.fr> - Pixware <http://www.pixware.fr>
Le Capricorne - 23 rue Colbert - 78180 Montigny-le-Bretonneux - France
voice: +33 (0)1.30.60.07.00 - fax: +33 (0)1.30.96.05.23
