Tony Pursell wrote:
...
Type in the text you want to hide, select it, then apply the
'invisible' format. You have to do it that way as I don't think you
can type anything with a hidden format selected.
I have tried this and can confim that the hidden text is in the
XML.
Like so:
He heard quiet steps behind him.
<text:span text:style-name="TagHidden">T07364</text:span>
The only problem is that's not what was asked for. What he wants, IIUC,
is a hidden 'tag' on visible text.
You can do this by attaching a style that doesn't change anything, where
the style name embeds the ID, something like
That may <text:span text:style-name="Tag:T07364">bode</text:span> well.
The problem(s) with that are:
1) It can be removed unintentionally very easily using the normal UI
(Format > Default)
2) It cannot be nested, another requirement was overlapping areas.
Both of these are also rather ugly hacks, bending the formatting tags to
do semantic markup.
In fact, that is one thing that ODF doesn't seem to do at all: allow you
to build custom document extensions on top of it. XML is made for that,
and ODF is XML, but ODF and OOo don't really give you access to the
underlying XML structure in a general way. Not that I can see anyway.
Another idea would be to insert fields. You can specify two field names:
Start_tag and End_tag and then use "Set Value" fields to give them ID's.
It would look like this, including two overlapping areas:
He heard quiet steps behind him.
<text:variable-set
text:name="Start_tag" text:display="none" office:value-type="string"
office:string-value="T07364"/>
That will bode well.
<text:variable-set
text:name="Start_tag" text:display="none" office:value-type="string"
office:string-value="T00133"/>
Who could be following him this late at night
and in this deadbeat part of town?
<text:variable-set
text:name="End_tag" text:display="none" office:value-type="string"
office:string-value="T00133"/>
And at this particular moment
<text:variable-set
text:name="End_tag" text:display="none" office:value-type="string"
office:string-value="T07364"/>
just after he pulled off the big time and was making off with the greenbacks.
The fields could be (optionally) invisible, and can encode overlapping
areas.
The GUI does not provide a way to search for fields, but I'm sure the
API will provide some way to do it.
I would worry that this will still be a very clumsy approach, since the
user can easily delete the tags by mistake, but I don't really know
enough about how the application will be used to know if that's a killer
problem.
<Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
