[Libreoffice-bugs] [Bug 126256] FORMATTING, FILEOPEN: Plain text document in (codepage 437) with commercial font displays incorrectly

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Tue Jul 23 12:55:13 UTC 2019


https://bugs.documentfoundation.org/show_bug.cgi?id=126256

V Stuart Foote <vstuart.foote at utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |NEEDINFO

--- Comment #7 from V Stuart Foote <vstuart.foote at utsa.edu> ---
Sorry, I am not intentionally being negative in setting this NAB, there just is
no way to put it that does not point to incorrect usage of the os/DE and
LibreOffice features for import of this type of text document.

(In reply to robert from comment #5)
> 
> Completely irrelevant reply. I open it like I would with Word. LO should
> allow me to follow exactly the same steps!

Sorry, but it would if you make a file association for an .h-c file extension
in the os/DE or change the extension. But you'd still have to select the
encoding.

(In reply to robert from comment #6)
> 
> Nice to be so negative, calling it 'document'. It's plain text, one
> paragraph per line and a monospace font. Is that not a format?

When imported via the "Text - Choose Encoding (.txt)" filter after selecting
its encoding, LibreOffice will assign defaults for the 'Preformatted text'
style laid out on the default 'Page' style. 

And if you adjust those style defaults (either in advance, or after import) the
document will be correctly laid out with no need to select content and apply
direct formatting.

That includes making an assignment of the mono spaced Cubiculum font mentioned
for use as the 'Preformatted text' style if prefered to default Liberation
Mono. 

Or you could select other common monospaced fonts Noto Mono, Courier New,
Consolas, etc.  The allignment of the Box line drawing glyphs would be
controlled by each font's metrics--so always some potential for gaps.

All of these are usage issues.

LibreOffice is doing the correct thing on import of the text with correct
filter.

Would you please clearly state what you think the issue is.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190723/86d12f96/attachment.html>


More information about the Libreoffice-bugs mailing list