Dear Kyle,
> Kyle Meyer writes:
> Thanks for reporting back. Arne sent an equivalent patch (see
> sibling thread), verifying that LibreJS worked with it. I applied
> that in 661696036 (ox-html: escape & in license magnets,
> 2020-03-15), so we should be all set.
I've done a
Hi Colin,
Colin Baxter writes:
>> Kyle Meyer writes:
> > Colin, could you try exporting with the change below and see if
> > that resolves your validation issues? It'd also be great if you
> > could check whether librejs is still happy after that change.
>
> I've now applied t
> Kyle Meyer writes:
> Adam Porter writes:
>> Colin Baxter writes:
>>
>>> In my opinion, if it can't be fixed then the changes should be
>>> removed. Surely, we cannot have an org-mode that knowingly
>>> exports/publishes something that causes a validation error!
> Kyle Meyer writes:
> Adam Porter writes:
>> Colin Baxter writes:
>>
>>> In my opinion, if it can't be fixed then the changes should be
>>> removed. Surely, we cannot have an org-mode that knowingly
>>> exports/publishes something that causes a validation error!
Arne Babenhauserheide writes:
> And second: I just verified that LibreJS still recognizes the license
> when we escape the & as &
>
> I would suggest the following:
>
> diff --git a/lisp/ox-html.el b/lisp/ox-html.el
Great, thanks the suggestion and verifying the LibreJS recognizes it.
That it ma
Dear Kyle, Dear Colin,
Colin Baxter writes:
> >> ./lisp/ox-html.el:235:// @license
> >>
> magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt
> >> GPL-v3-or-Later
> > [...]
> >> I think the culprit is commit
> >> 68fa5e589f00c8d5b4f7f0dc70be6ebe592
Adam Porter writes:
> Colin Baxter writes:
>
>> In my opinion, if it can't be fixed then the changes should be
>> removed. Surely, we cannot have an org-mode that knowingly
>> exports/publishes something that causes a validation error!
>
> Looking at the error message, the fix might be very simp
Colin Baxter writes:
> In my opinion, if it can't be fixed then the changes should be
> removed. Surely, we cannot have an org-mode that knowingly
> exports/publishes something that causes a validation error!
Looking at the error message, the fix might be very simple:
The most common cause of
Dear Kyle,
Thanks for your reply.
> Kyle Meyer writes:
> Colin Baxter writes:
>> - Begin - Warning Line 205, Column 74: cannot generate
>> system identifier for general entity "dn"
>>
>> …rn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt
>> GP
Colin Baxter writes:
> - Begin -
> Warning Line 205, Column 74:
> cannot generate system identifier for general entity "dn"
>
> …rn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt
> GPL-v3-or-Later
>
> An entity reference was found in the document, but there is no
>
There is no error using org-mode built in the emacs-28.0.50 so it does
look as if commit 68fa5e589f00c8d5b4f7f0dc70be6ebe59238bb8 is the culprit.
Is it only me using http://validator.w3.org/check?
Best wishes,
--
Colin Baxter
www.Colin-Baxter.com
Publishing with Org mode version 9.3.6 (release_9.3.6-419-gd9b1fb) I get
an validation error using http://validator.w3.org/check. The error is:
- Begin -
Warning Line 205, Column 74:
cannot generate system identifier for general entity "dn"
…rn:btih:1f739d935676111cfff4b4693e3816e664797
12 matches
Mail list logo
