asciidoctor-pdf problem after upgrade to asciidoctor 1.5.6: "failed to parse formatted text"

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

asciidoctor-pdf problem after upgrade to asciidoctor 1.5.6: "failed to parse formatted text"

jvdh
after upgrade to asciidoctor 1.5.6, asciidoctor-pdf fails with error messages such as

Failed to parse formatted text: a & times; b

wenn the document contains HTML character entities such as "& times;". is this a known issue?



thank you,

joerg
Reply | Threaded
Open this post in threaded view
|

Re: asciidoctor-pdf problem after upgrade to asciidoctor 1.5.6: "failed to parse formatted text"

mojavelinux
Administrator
Does the document contain the glyph or a character reference? It would be easiest if you shared the snippet of AsciiDoc that contains the character so I understand the context.

This issue is news to me. But I'm not sure yet how to reproduce what you're encountering.

Cheers,

-Dan

On Fri, Jul 14, 2017 at 2:43 AM, jvdh [via Asciidoctor :: Discussion] <[hidden email]> wrote:
after upgrade to asciidoctor 1.5.6, asciidoctor-pdf fails with error messages such as

Failed to parse formatted text: a × b

wenn the document contains HTML character entities such as "×". is this a known issue?

thank you,

joerg


To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Dan Allen | @mojavelinux | https://twitter.com/mojavelinux
Reply | Threaded
Open this post in threaded view
|

Re: asciidoctor-pdf problem after upgrade to asciidoctor 1.5.6: "failed to parse formatted text"

jvdh
sorry for the confusion (I've edited the original post in the meantime to avoid unintended glyph display ..): the test documents entire content is
 
//cut here
a {some_character_entitity_reference} b
//cut here

I've tried `& times;' and `& beta;' but probably others don't work either. so I am talking of the character reference/symbolic name, not the glyph.
 
and I am only guessing that it is related to the 1.5.6 upgrade (it did work before the upgrade and it does not now), but I have not yet "downgraded" back to 1.5.5 to double check if 1.5.5. still works now ;-)... if relevant: this is seen on osx 10.12/ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16]
 
thank you,
 
joerg
Reply | Threaded
Open this post in threaded view
|

Re: asciidoctor-pdf problem after upgrade to asciidoctor 1.5.6: "failed to parse formatted text"

mojavelinux
Administrator
Asciidoctor PDF does not support named character references (other than the built-in ones in XML like &gt;). You must use numeric references.

a &#215; b

It's on the roadmap to support other variants.

Do you get a warning if you use the numeric reference?

-Dan

On Fri, Jul 14, 2017 at 3:21 AM, jvdh [via Asciidoctor :: Discussion] <[hidden email]> wrote:
sorry for the confusion (I've edited the original post in the meantime to avoid unintended glyph display ..): the test documents entire content is
 
//cut here
a {some_character_entitity_reference} b
//cut here

I've tried `& times;' and `& beta;' but probably others don't work either. so I am talking of the character reference/symbolic name, not the glyph.
 
and I am only guessing that it is related to the 1.5.6 upgrade (it did work before the upgrade and it does not now), but I have not yet "downgraded" back to 1.5.5 to double check if 1.5.5. still works now ;-)... if relevant: this is seen on osx 10.12/ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16]
 
thank you,
 
joerg


To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Dan Allen | @mojavelinux | https://twitter.com/mojavelinux
Reply | Threaded
Open this post in threaded view
|

Re: asciidoctor-pdf problem after upgrade to asciidoctor 1.5.6: "failed to parse formatted text"

jvdh
On Fri, 14 Jul 2017 11:33:26 +0200, mojavelinux [via Asciidoctor ::  
Discussion] <[hidden email]> wrote:

>
>
> Asciidoctor PDF does not support named character references (other than  
> the
> built-in ones in XML like &gt;). You must use numeric references.

oh... I see.

>
> a &#215; b
>
> It's on the roadmap to support other variants.

great!

>
> Do you get a warning if you use the numeric reference?

no more parse errors, you are right, of course...

so it seems that I had a misconception about it working prior to 1.5.6 and  
that I simply just used character entities with asciidoctor-pdf (rather  
than asciidcoc/dblatex...) for the first time right after the upgrade to  
1.5.6 ....

sorry for the noise.

joerg

>
> -Dan
>
> On Fri, Jul 14, 2017 at 3:21 AM, jvdh [via Asciidoctor :: Discussion] <
> [hidden email]> wrote:
>
>> sorry for the confusion (I've edited the original post in the meantime  
>> to
>> avoid unintended glyph display ..): the test documents entire content is
>>
>> //cut here
>> a {some_character_entitity_reference} b
>> //cut here
>>
>> I've tried `& times;' and `& beta;' but probably others don't work  
>> either.
>> so I am talking of the character reference/symbolic name, not the glyph.
>>
>> and I am only guessing that it is related to the 1.5.6 upgrade (it did
>> work before the upgrade and it does not now), but I have not yet
>> "downgraded" back to 1.5.5 to double check if 1.5.5. still works now  
>> ;-)...
>> if relevant: this is seen on osx 10.12/ruby 2.0.0p648 (2015-12-16  
>> revision
>> 53162) [universal.x86_64-darwin16]
>>
>> thank you,
>>
>> joerg
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://discuss.asciidoctor.org/asciidoctor-pdf-problem-
>> after-upgrade-to-asciidoctor-1-5-6-failed-to-parse-
>> formatted-text-tp5719p5721.html
>> To start a new topic under Asciidoctor :: Discussion, email
>> [hidden email]
>> To unsubscribe from Asciidoctor :: Discussion, click here
>> <
>> .
>> NAML
>> <
http://discuss.asciidoctor.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
>


--
Using Opera's revolutionary email client: http://www.opera.com/mail/
Reply | Threaded
Open this post in threaded view
|

Re: asciidoctor-pdf problem after upgrade to asciidoctor 1.5.6: "failed to parse formatted text"

mojavelinux
Administrator
No problem at all. I'm glad to help!

Cheers,

-Dan

--
Dan Allen | @mojavelinux | https://twitter.com/mojavelinux