I get that with @ref completion but was wondering whether it would work
via @ident and know where to point (well, it might start with the string
value of the targeted element, for one thing, but knowing the oXygen
guys it could be way smarter... I think I want to check this out... :-) ).
On 17/11/15 17:14, James Cummings wrote:
> On 17/11/15 15:57, Piotr Bański wrote:
>> On 17/11/15 13:29, James Cummings wrote:
>>> Now, I know what your answer will be: We
>>> want human-readable and encodable private URI values, no encoder can
>>> type in 300011851 and know what it means.
>> Unless you use smart content completion. I wonder... That would
>> require a layer of configurable redirection inside a smart editor,
>> right? To provide a list of values (potential fillers) with their
>> descriptions taken from designated elements.
> I believe this could already be done in oXygen Author Mode -- perhaps it
> could also be done in the Text/XML mode as well with a plugin, I'm not