![]() I don’t fully understand what you’ve done to Heading 2. your 'See attachment" paragraphs at level two are aligned with heading 2 title but end up flushed at left margin in HTML because tabs heave been removed). This means that your level dependent left indent requires one style per level. This must be managed exclusively through paragraph styles. ![]() In Numbering tab, for all used levels, set Sparator After to a space. Since tabs are ignored by the output filter, set Number followed by Nothing in Tools> Chapter Numbering, Position tab. But, considering you already spent a lot of time on the real document, there are several workarounds. Ideally, you should restart from scratch. html, the dialog warned you about the possible loss of formatting effects? Have you noticed, the first time you saved as. If you had chosen from start File> New> HTML Document,Īll menus and formatting actions would have been downgraded to HTML capabilities. The first difference: from pages to continuous stream.Ī second difference, of utmost importance in your case: HTML has no notion of tab stops consequently tabs are simply ignored (they could have been translated into a space but the output converter has not chosen this path). html format, the document will be approximately translated from ODF concepts to HTML concepts. odt document, you format a common paginated to-be-printed document. However, as I explained, File> New Text Document and File> New> HTML Document are different and launch different LO components. I had a look at the attached sample file. You still control Writer through its styles (full or reduced capabilities) and these styles are translated, perhaps not as you would like, by an export filter (may be approximate remember: Traduttore, traditore). However, in both cases, you don’t edit directly HTML markup. I conducted my test in the second context. In the second case, you start directly into HTML formatting with simplified styles corresponding to W3C standards. In the first case, you edit a sophisticated formatted document which is converted into an HTML one with embedded CSS directives trying to mimic Writer styles. odt is not the same as File> New> HTML Document then save! To summarise: no bug in Writer/HTML but a misconception of yours about differences between HTML edition and document edition (and also a different base configuration in those components).ĬAUTION! Save as. They will translate to CSS to be rendered in a portable way by browsers. But you can always define custom ones for your needs. Note that there are far less built-in styles in Writer/HTML component than in Writer. This will translate to CSS and give highly predictable results. It is much better, safer and reliable to use styles (or as a fallback, cursors in the horizontal ruler). This is intended behaviour in browsers.Īnyway, in Writer or browsers, it is always a bad idea to indent paragraph with spaces. However, if you use ordinary spaces for your indent, those spaces are also present in the HTML (Writer takes no initiative about that and you can’t blame it), but W3C says that any sequence of ordinary spaces is considered as a single space and browsers render it accordingly (eventually stretching ALL spaces in a line to justify adge to edge). ![]() If indent is made with NBSP, those NBSP are present in the resultant HTML and rendered as expected. Configure all your levels, notably the separator before and after parameters. Consider they are separate applications settings-wise. The settings you may have customised in Writer are not forwarded to the HTML editor. You must configure the properties of chapter numbering with Tools> Chapter Numbering.
0 Comments
Leave a Reply. |