SoylentNews is people
SoylentNews
Blogger Dedoimedo is known for his fascination with bling and his attention to compatibility with MICROS~1's pseudo-standards. So, how did the most recent version of the popular FOSS office suite fare in his test?
LibreOffice 4.4 review - Finally, it rocks
[...]As a free, open-source and cross-platform solution, LibreOffice allows people to enjoy the world of writing, spreadsheets, presentations, and [the like] without having to spend hefty sums of money. The only problem till now was that it didn't quite work as advertised. Microsoft Office support was, for the lack of a better word, lacking.
[...] The most important part, [it now has] Microsoft Office support
[...]my 182-page [DOCX] document, full of images, references, footnotes, preformatted code, and other cool elements, all of which were initially conceived in LaTeX then transformed to PDF and finally to DOCX looked pretty much spotless. The image quality was a little low, but it has nothing to do with LibreOffice. I was amazed. I had not expected this, and it seems for the first time ever, LibreOffice is a most viable solution for home office use. Blimey.
LibreOffice 4.4 is everything you could have hoped for, and then some. It's beautiful. It's streamlined. It has an improved UI, which offers much more intuitive work flows, resulting in an immediate boost in productivity. It comes with enhanced menus, a more intelligent way of working with styles, easier graphics, copy & paste options, a simpler method of polishing up presentations. Most importantly, it offers a genuinely good support for the proprietary Microsoft file formats, allowing you, for the very first time, to consider LibreOffice as the one and only office suite you'll ever need.
I have never quite expected this. In fact, LibreOffice 4.4 should have been called 5.0, because it is that much better. Perhaps grander changes are needed to justify a full new release. Just think of the possibilities, if we got all this in a single dot revision. Imagine what will happen when LibreOffice finally matures toward the next large release.
One wonders how long it will be till MSFT alters their "standard" so that compatibility is broken again.
(Score: 5, Interesting) by HyperQuantum on Tuesday February 24 2015, @07:48PM
While I agree that "MICROS~1" in the summary is quite bad taste, I feel I must emphasize that 8.3 names are still an issue today, unfortunately.
One example is the Directory.GetFiles [microsoft.com] method in the .NET framework:
Note:
Because this method checks against file names with both the 8.3 file name format and the long file name format, a search pattern similar to "*1*.txt" may return unexpected file names. For example, using a search pattern of "*1*.txt" returns "longfilename.txt" because the equivalent 8.3 file name format is "LONGFI~1.TXT".
IMHO such an old technicality should not be exposed in a supposedly modern API like .NET.
(Score: 2) by hash14 on Wednesday February 25 2015, @12:31AM
And here is a great example of how bad design decisions can still be a problem decades later. I'll have to keep this one in mind...