RIP Microsoft WordPad
gizmodo.com
RIP Microsoft WordPad
1–10 of 100 posts
Re: RIP Microsoft WordPad
#2I mentioned this in a prior HN thread on this:
Rip C:\Program Files\Windows NT\Accessories and back it up somewhere. WordPad.exe is standalone. If you're running Win7+ you'll need the en-us/muis/etc, if you pull from an XP install wordpad.exe is all you'll ever need to do.
Bonus points if you just grab a Windows XP iso and deflate wordpad.exe from the install image - copy WORDPAD.EX_ from the i386 folder and just run "expand wordpad.ex_ wordpad.exe".
Re: RIP Microsoft WordPad
#3Man people are nostalgic about the most bizarre things sometimes. My experience with WordPad was accidently opening something with it and having to change the default app for some extension.
Re: RIP Microsoft WordPad
#4We used to use RTF for walls text in our game launcher (EULA, MOTD etc). We chose RTF because raw Win32 could render it without extra work and we wanted to minimize both launcher complexity and dependencies.
One thing we noticed was that RTF documents made in WordPad instead of Word were much, much smaller and since every byte added to our CDN bill we made a point of re-saving all our files in WordPad before publishing them. Sometimes simple is good.
Re: RIP Microsoft WordPad
#5[deleted]
Re: RIP Microsoft WordPad
#6We used to use RTF for walls text in our game launcher (EULA, MOTD etc). We chose RTF because raw Win32 could render it without extra work and we wanted to minimize both launcher complexity and dependencies. One thing we noticed was that RTF documents made in WordPad instead of Word were much, much smaller and since every byte added to our CDN bill we made a point of re-saving all our files in WordPad before publishi…
Word was not able to open correctly RTF file until recently.
Re: RIP Microsoft WordPad
#7Man people are nostalgic about the most bizarre things sometimes. My experience with WordPad was accidently opening something with it and having to change the default app for some extension.
This article is definitely hamming it up to fill an article about a single line in a change log.
I don’t know if anyone is emotional about this. At worst maybe someone is vaguely annoyed that they will have to change their workflow that invariably involves .rtf files for some reason.
Re: RIP Microsoft WordPad
#8Man people are nostalgic about the most bizarre things sometimes. My experience with WordPad was accidently opening something with it and having to change the default app for some extension.
The only use case I have ever used Wordpad for was to open text files with Linux End-of-Lines on a Windows computer with only Wordpad and Notepad (that do not see LF as proper and of lines and just displays one line of mess).
Re: RIP Microsoft WordPad
#9Wordpad is usually my go to when opening a unix text file (without carriage returns) that Notepad renders into a unintelligible mess. Word renders it properly, but then typically requires a bunch of subsequent formatting adjustments (font size, etc.) for good readability.
Re: RIP Microsoft WordPad
#10Man people are nostalgic about the most bizarre things sometimes. My experience with WordPad was accidently opening something with it and having to change the default app for some extension.
The only use case I have ever used Wordpad for was to open text files with Linux End-of-Lines on a Windows computer with only Wordpad and Notepad (that do not see LF as proper and of lines and just displays one line of mess).
Same here. Open a text file in Notepad and the contents extend way past the edge of the screen. Open it in WordPad and turn on line wrapping.
Oh! Also, needing to open an RTF when Word wasn't installed.