Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Alan Stern wrote:
On Fri, 17 May 2013, Girvin R. Herr wrote:

Alan Stern wrote:
Here's another odd thing I encountered.  Moving the cursor one
character at a time (using the right-arrow key), I find what appears to
be two hidden characters: one at the beginning of the readonly field
and one at its end.

That is, start with the cursor just to the left of the blank space
before the "(9)" field.  Pressing right-arrow advances the cursor to
the right of the space, leaving it on the left-hand edge of the '('. Pressing right-arrow again doesn't move the cursor at all. Pressing it
once more advances the cursor between the '(' and '9'.

Alan Stern
Did you try viewing hidden objects?
Check the following:
View -> Field Names
View -> Nonprinting Characters
View -> Hidden Paragraphs

I have tried these.  They make no difference.

Maybe one of those will make your "hidden characters" visible and give you a clue as to what it is doing.


Another more painful option could be to unzip the file and look at the text to see what is there at these "hidden" characters, optionally editing it out manually.

Interesting; I didn't know one could do that. The content.xml file shows the following (the "..." part is where I erased a lot of irrelevant material; I also wrapped a couple of long lines):

<text:span text:style-name="T3"> </text:span>
<field:fieldmark-start text:name="__Fieldmark__24_1596095481"
<field:param field:name="vnd.oasis.opendocument.field.code"
 field:value=" ADDIN EN.CITE &lt;EndNote&gt; ... "/>
<field:param field:name="" field:value="81"/>
<text:span text:style-name="T5">(9)</text:span>
<text:span text:style-name="T1"> </text:span>
<text:span text:style-name="T2">Normal again.

I don't know enough to interpret all that, but clearly there is a field of a sort that LibreOffice isn't ready to handle.

Is there some way to get this information from within LibreOffice itself? I would that the field name and/or value should be accessible.

Third, maybe another ODF processor, such as KDE's editor, Kword, may not support this readonly attribute and allow you to edit it normally.

Maybe.  I don't see where in there the field is marked as readonly.

Alan Stern
I am not an expert in decoding the XML for LO. Maybe someone else on the list can explain that. Even though there is no "smoking gun" reference to a "readonly" attribute, there do seem to be a lot of numbers in your snippet above that could mean something to LO. On the other hand, I am not sure what LO would do when it encounters something it doesn't understand. One option for it is to protect the information just to be sure, and that could be what you are seeing. I am guessing.

Of course, you could make a test copy of this file and just try changing suspicious things on the copy and see what LO does. Painful, but instructive.

Didn't you say this file had been converted from MSWORD? If so, and LO did the conversion, there may indeed be a bug in the converter that needs to be brought to the attention of the devs.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.