Hello,
Aaron Ecay <aarone...@gmail.com> writes:
> Hi Nicolas,
>
> 2015ko otsailak 15an, Nicolas Goaziou-ek idatzi zuen:
>>> 1) It looks like it only supports properties directed at specific
>>> backends. How should users specify custom properties that they want to
>>> be handled in multiple backends (by their own filter)?
>>
>> They cannot (unless they want to use something like "|custom: ...").
>>
>> Note they cannot either for regular elements using attributes. The
>> reason is that multiple back-end properties are very rare. For
>> example, :width hasn't the same unit in "ox-latex" and "ox-html".
>
> It seems like these might occur for citations. The :capitalize property
> discussed in the predecessor to this thread is one example. So perhaps
> there could be a |all: list which would be merged with the
> backend-specific one(s).
Perhaps. But [cite: ... |latex: :cap t |html: :cap t] isn't impossible
to write either.
Anyway, time for another proposal. In fact, it seems that it would be
better to externalize these properties, e.g.,
[cite: ...]{latex :prop val}{html :prop val}
or
[cite: ...]{latex :prop val | html :prop val}
No space allowed between the citation and the attributes. The big
advantage with this is that it can be extended to other objects while
still being backward-compatible.
It would solve one long standing limitation:
Text [[file:img1.png]]{html :width 50px} and
[[file:img2.png]]{html :width 60 px}
Regards,
