Re: [O] format of the ID property in the new HTML exporter
Hi Florian, Florian Beck f...@miszellen.de writes: Yes. Why do you need the assert? It only seems to be there to make my life more difficult. I've remove the (assert ...) sexp, which was too strict, I agree. Thanks, -- Bastien
Re: [O] format of the ID property in the new HTML exporter
Jambunathan K kjambunat...@gmail.com writes: There is ID and then there is CUSTOM_ID. IIUC/IIRC, ID is a uuid and CUSTOM_ID can be whatever. Any reason why you cannot use CUSTOM_IDs here? Yes. Why do you need the assert? It only seems to be there to make my life more difficult. -- Florian Beck
Re: [O] format of the ID property in the new HTML exporter
Daniel Clemente n142...@gmail.com writes: Hi, in ox-html.el there's a line with an assert (the only one): (assert (org-uuidgen-p path)) 1. I have some IDs like o5y98600aze0 which don't conform to that uuidgen format; they were created by early versions of org. Should only UUIDs be accepted as ID? 2. I think the ID should be editable by hand to what you like, as long as they are unique. If you don't need to export it you don't need a CUSTOM_ID, and having both ID and CUSTOM_ID is not the simplest way. So I think that assert is too strict. My short IDs seem as good as the long UUIDs. There is ID and then there is CUSTOM_ID. IIUC/IIRC, ID is a uuid and CUSTOM_ID can be whatever. Any reason why you cannot use CUSTOM_IDs here? --
[O] format of the ID property in the new HTML exporter
Hi, in ox-html.el there's a line with an assert (the only one): (assert (org-uuidgen-p path)) 1. I have some IDs like o5y98600aze0 which don't conform to that uuidgen format; they were created by early versions of org. Should only UUIDs be accepted as ID? 2. I think the ID should be editable by hand to what you like, as long as they are unique. If you don't need to export it you don't need a CUSTOM_ID, and having both ID and CUSTOM_ID is not the simplest way. So I think that assert is too strict. My short IDs seem as good as the long UUIDs.
