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


The UI Instructions are correct, if a little terse.

The missing key is that the document must be a valid .HTM or .HTML file
type. Done to a ODF formated document, by either *Export *to  XHTML, or by
using the*Save as* and selecting the HTML Document  (Writer) and allowing
the conversion to other than ODF format.

<http://nabble.documentfoundation.org/file/n4065381/SavaAs_convertToHTML%28Writer%29dialog.jpg> 

So either "export" to HTML or  "save a copy" of an .ODT  file being edited
to HTML.  Simply renaming using Widnows Explorer won't do the conversion, it
needs to actually be HTML. 

 Then when being edited in Writer, the "View" menu will show the "HTML
source". 

<http://nabble.documentfoundation.org/file/n4065381/Menu_VeiwHTML.jpg> 

Which can also be toggled with an <ALT>+V, <ALT>+M accelerator when document
has been detected as valid  HTML or XHTML.



--
View this message in context: 
http://nabble.documentfoundation.org/HTML-Source-tp4065331p4065381.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.