Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

how to specify control caching using HTML meta

I have many .odt docs that I design in odt and then save as HTML. I am using LibreOffice 3.5.7.2. Requirements: (1) to be able to edit the document or to cenvert the document to odt because that is where I do 98% of the work. (2) Insert cache control meta tags.

I have a need to specify some meta tags that control caching using HTML meta such as: <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"/> There are 2 ways to do it. (1) I can use plain text editor in the HTML form, then use LibreOffice to convert the document HTML to odt so that I can continue my editing in odt. If I do that, LibreOffice eats those tags. They just disappear. (2) I can use LibreOffice in .odt format and use the file |properties | custom-properties section to insert HTML tags. Unfortunately I do not see how to insert tags that are more complex than what the “properties” editor can handle which is it can only handle form name=”text”. Any reasonable suggestion will be appreciated. -thanks for reading

how to specify control caching using HTML meta

I have many .odt docs that I design in odt and then save as HTML. I am using LibreOffice 3.5.7.2. Requirements: (1) to be able to edit the document or to cenvert the document to odt because that is where I do 98% of the work. (2) Insert cache control meta tags.

I have a need to specify some meta tags that control caching using HTML meta such as: <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"/> There are 2 ways to do it. (1) I can use plain text editor in the HTML form, then use LibreOffice to convert the document HTML to odt so that I can continue my editing in odt. If I do that, LibreOffice eats those tags. They just disappear. (2) I can use LibreOffice in .odt format and use the file |properties | custom-properties section to insert HTML tags. Unfortunately I do not see how to insert tags that are more complex than what the “properties” editor can handle which is it can only handle form name=”text”. Any reasonable suggestion will be appreciated. -thanks for reading