Live data from Hacker News

Microsoft is killing WordPad in Windows

bleepingcomputer.com

361–367 of 367 posts

Re: Microsoft is killing WordPad in Windows

#361

Earlier quoted context omitted.

95% of the patches __are__ bugfixing. New features are pretty rare. We're mostly volunteers, so people implement whatever they feel like doing :-) The essence of open-source. Come help out if you can, or sponsor some fixes with one of the LibreOffice consulting companies.

"We're mostly volunteers, so people implement whatever they feel like doing :-) The essence of open-source." I am extremely appreciative of what open-source developers do. One only has to look at the Linux ecosystem to see how much work they've contributed—and of course there's much more than just that. What you say is obvious, volunteers are unlikely do work they do not like and I'd certainly not expect them to do s…

Unfortunately tables are a major weak point in the writer codebase.

Hopefully you will be happy to hear that a company has funded some improvements to that part of the code, and those improvements should roll out over the current and the next release.

ODT files are theoretically human-editable, because once you expand the file (using e.g. unzip) you have a small set of XML files, which can be edited as text and then wrapped up into an ODT again.

Finding "corruption" is not really a thing (at least for writer documents), the spec for writer documents is sufficiently complex that parts of it are in conflict with itself, and compromise solutions must be found in the code.

The writer code to lay the document out is sufficiently complex that it has multiple chunks of guard code specifically designed to make it give up when it cannot make reasonable progress.

Re: Microsoft is killing WordPad in Windows

#362

Earlier quoted context omitted.

"We're mostly volunteers, so people implement whatever they feel like doing :-) The essence of open-source." I am extremely appreciative of what open-source developers do. One only has to look at the Linux ecosystem to see how much work they've contributed—and of course there's much more than just that. What you say is obvious, volunteers are unlikely do work they do not like and I'd certainly not expect them to do s…

Unfortunately tables are a major weak point in the writer codebase. Hopefully you will be happy to hear that a company has funded some improvements to that part of the code, and those improvements should roll out over the current and the next release. ODT files are theoretically human-editable, because once you expand the file (using e.g. unzip) you have a small set of XML files, which can be edited as text and then…

Thanks for responding and being so quick about it. In fact, I was still fixing typos and adding a bit at the end when you replied so you may have missed that bit.

Very good to hear about the table improvements, I look forward to seeing them.

Re ODT, I unzipped it and looked at the XML and the stuff in the table section was formatted so badly (tightly together as one huge blob of text sans proper spaces and structured formatting). Given the ODT is over 900k long and having examined the XML for an hour or so I simply gave up. I hate to think how long it would have taken me to examine it in detail let alone resolve it without me first going crazy.

As I was in a desperate hurry I cut my losses and used my time fixing it in a way where I could at least estimate the time required.

"the spec for writer documents is sufficiently complex that parts of it are in conflict with itself,"

This sounds like what was happening, in parts of the table when paging up or down between pages sections of text (both within a cell with multiple lines of text and across cells in lines before and after). Text in a cell would mix and fold over itself or fold over the text in the cell in the line above or below it. Given that some cells could have text of several hundred lines in length sections of the table (but not all of it) became an almighty jumbled mess.

Right, at times it just gave up and if it didn't resolve (respond to commands within a minute or so) I killed it with the task manager.

Re: Microsoft is killing WordPad in Windows

#363

Earlier quoted context omitted.

pdf and rtf are totally different things. rtf is nearer html - in fact Apple Mail changed from rtf to html in very early OSX possibly 10.3

Sure but PDF seems to have replaced RTF in some ways. When you used to download software it would often come with an RTF file as documentation, now it would be a PDF.

Yes but not if you need editing which is what WordPad can do.

In this case we have an improved fuction as instructions should not be editable.

Re: Microsoft is killing WordPad in Windows

#364

Microsoft is slowly removing features, but is it adding any notable features? Here are some examples of features I would like to see: - Native Markdown viewer and editor, to replace Wordpad - Disk space manager - graphically show where my diskspace went; allow me to find and delete large files - Restartable and reliable file copy (similar to rsync on Linux) - Notepad with same features as textarea element in browser,…

> - Disk space manager - graphically show where my diskspace went; allow me to find and delete large files Try WinDirStat.

I rather run Directory Report over WinDirStat. DR can save more reports, Scan millions of files, Find duplicate files too

Re: Microsoft is killing WordPad in Windows

#365

Microsoft is slowly removing features, but is it adding any notable features? Here are some examples of features I would like to see: - Native Markdown viewer and editor, to replace Wordpad - Disk space manager - graphically show where my diskspace went; allow me to find and delete large files - Restartable and reliable file copy (similar to rsync on Linux) - Notepad with same features as textarea element in browser,…

> - Disk space manager - graphically show where my diskspace went; allow me to find and delete large files Try WinDirStat.

I rather run Directory Report than WinDirStat. DR can save more reports, Scan million of files, and find duplicate files

Re: Microsoft is killing WordPad in Windows

#366
post #257

Earlier quoted context omitted.

But doesn't a basic text editor like notepad++, or sublime text, I guess nowadays people use vscode too, take care of that? Why would you want to use some kind of rich text editing program for those?

So you have to go out and install third party software rather than just right click and open with WordPad, particularly when using someone else's computer, or a corporate system where you can't just install random software But the point is moot now that they added support for this to Notepad. Dunno if there are still supported versions of Windows out there that don't have it, but at least the newer systems should

Have they? I'll have to try now, or really.. I haven't worried in a long while, so it's probably had it a long time now.

Re: Microsoft is killing WordPad in Windows

#367
post #46

Which free/open source alfernatives to WordPad for Windows do you recommend then? LibreOffice is huge and slow, MS Office Online requires Internet. How to edit simple RTF/DOC documents offline on Windows without downloading >300MB full LibreOffice suite? Only Abiword comes to my mind.

Notepad++ maybe?

Notepad++ doesn't support RTF nor DOCX.
Post reply on HN