Re: [O] ox-html export bug

2017-09-09 Thread Nicolas Goaziou
Hello, Fabrice Popineau writes: > 2017-09-08 19:40 GMT+02:00 kadal : > >> That said, the first option is better because if I'm setting a CUSTOM_ID, >> that's what should be used for internal links... >> >> > I agree with that. Ideally, if you set a CUSTOM_ID, then it should replace > the default

Re: [O] ox-html export bug

2017-09-08 Thread Fabrice Popineau
2017-09-08 19:40 GMT+02:00 kadal : > On 09/08/2017 10:32 AM, Nicolas Goaziou wrote: > >> kadal writes: >> >> Seems like the second one should export to either "" >>> or "". >>> >> >> Is it valid HTML? >> >> Regards, >> >> This SO thread has confusing answers: https://stackoverflow.com/ques > tion

Re: [O] ox-html export bug

2017-09-08 Thread kadal
On 09/08/2017 10:32 AM, Nicolas Goaziou wrote: kadal writes: Seems like the second one should export to either "" or "". Is it valid HTML? Regards, This SO thread has confusing answers: https://stackoverflow.com/questions/192048/can-an-html-element-have-multiple-ids#192066 Looks like th

Re: [O] ox-html export bug

2017-09-08 Thread kadal
Fair point. Would it be sufficient to give these type of links a class, say "org-internal-links". Then you should be able to explicitly turn off the content for these links. .org-internal-links::after {content:"";} I don't know, looks like a bug to me. I haven't put much thought into

Re: [O] ox-html export bug

2017-09-08 Thread Nicolas Goaziou
kadal writes: > Seems like the second one should export to either "" > or "". Is it valid HTML? Regards,

Re: [O] ox-html export bug

2017-09-08 Thread Nicolas Goaziou
Hello, Rasmus writes: > kadal writes: > >> The problem is that if you have CSS that decorates links by adding >> content after a link, that (empty) link gets decorated too. > > Fair point. Would it be sufficient to give these type of links a class, > say "org-internal-links". Then you should

Re: [O] ox-html export bug

2017-09-08 Thread Rasmus
kadal writes: > The problem is that if you have CSS that decorates links by adding > content after a link, that (empty) link gets decorated too. Fair point. Would it be sufficient to give these type of links a class, say "org-internal-links". Then you should be able to explicitly turn off the

[O] ox-html export bug with CUSTOM_ID

2017-09-07 Thread Deepak Cherian
This org file (OPTIONS are to keep the exported file clean) - * heading 1 * heading 2 :PROPERTIES: :CUSTOM_ID: my-name :END: exports to --- 1 heading 1 class="section-number-2">2 heading 2

Re: [O] ox-html export bug

2017-09-07 Thread kadal
The problem is that if you have CSS that decorates links by adding content after a link, that (empty) link gets decorated too. Is it possible to remove it? There is no such empty link for the first heading which does not have CUSTOM_ID set. Deepak On 09/07/2017 10:32 AM, Nicolas Goaziou wrot

Re: [O] ox-html export bug

2017-09-07 Thread Nicolas Goaziou
Hello, kadal writes: > This org file > > - > * heading 1 > * heading 2 > :PROPERTIES: > :CUSTOM_ID: my-name > :END: > > > > exports to > > --- > > 1 heading 1 > > > > class="section-number-2">2 heading 2

[O] ox-html export bug

2017-09-07 Thread kadal
This org file - * heading 1 * heading 2 :PROPERTIES: :CUSTOM_ID: my-name :END: exports to --- 1 heading 1 class="section-number-2">2 heading 2 --- The "