Except for my use case, which is when you have a 1,200 page document with hundreds of tables, lists, and pictures. The thing grinds to a halt and has all sorts of problems. Yes, I know that MS Word is not the best choice for documents that big, but it's not up to me.
"which is when you have a 1,200 page document with hundreds of tables, lists, and pictures"
This is like saying that SQLite is not a good product because you are using it on a Terabyte database having 1,000,000 hits at the same time... It might work but it would have problems because wasn't designed for that scenario.
I sympathize with you though... since it is not your decision :/
Have you tried the 64-bit version? People still normally install the 32-bit version (mainly for add-on supportability), but if you're working with very large documents, the 64-bit version should work better for you.
That's weird you can't break it down into smaller parts? I worked on a big book, about that size with several people and the major, mainstream publishing company wanted it in individual documents mapping to individual chapters.
We actually did break it up into several parts when making and editing it, but for the "official release" of the document (It's a big-ass test procedure document), they wanted it in one file. And of course there's always some changes you find after you release something.
A document that large must have some kind of a structure that you and your team can use to break it apart into smaller, more manageable chunks. One thing to consider is to place the content into a content management system of kind (a wiki comes to mind) to allow the content to more easily be maintained and grow without the limitations Word creates.
The decision may not have been up to you to keep it all in one Word document but making the case to either break apart the document or find a better system in which to maintain it ought to be easy in the face of the usability issues you mention.
Deleting my long rant here. It’s not really on topic for this thread. Suffice to say, I think MS Word is a pile of junk. For the curious: http://pastie.org/9297613
I used Office 2010 for a while and it was crashing 4+ times a day, so I tried 2013 and easily recreated some of those crashes. I have not used it extensively but it does not take long to discover it's still trash.
PS: Office 2013 still has bugs from word 97, which is what happens when there is zero competition.
[Sorry that this is all quite off topic for a conversation about surface.]
So imagine you have 4 authors: person A writes a document, and person B makes one set of changes, while person C makes a different set of changes, with person D working off of C’s version. Now person A wants to accept some but not all of C’s changes, and some but not all of B’s changes, and person D wants to “rebase” his document to add the changes that A approved from B and C, but not the changes that A did not approve...
How do you handle it? You’re saying MS word now has a solution for this that avoids conflicts? I guess I’m not enough of a power user to know about it.
Okay, now imagine that you want to both want to open and type on the same document at the same time, real-time-collaboration style. You’re saying Word has a solution for this one too?
Not sure about the first but for the second Office online does that now. Not sure if you can do it completely in the desktop app but the online UI isn't horrible from what I've used of it.
The first is basically a rather complicated workflow that is handled for instance with plain text documents in git. I doubt Word can do that (wouldn't know, haven't used it for a long time), after all it's core thing is being a word processor.
Now I didn't read your rant, but ranting that something is a pile of junk and then using a rather far-fecthed missing feature as an example of why it is a pile of junk, as a counter-argument to someone questioning your reasoning, is not proper logic. Can't think of a proper analogy atm, but claiming git is a pile of junk and then coming up with git diff not being able to deal with Word files as one of the reasons would probably come close: it makes no sense.
Word has great co-authoring support if you use Word Online (free equivalent of Google Docs which the desktop/tablet/phone client can work with natively), SharePoint, or Office 365.
I like Excel as much as the next guy, but even in 2013 when you open a delimited text file it makes you manually tell it what the delimiters are. A computer should be able to guess whether a large text file is CSV, TSV, etc. This is an example of something Apple would get right, but Microsoft does not, even after more than a decade with this heavily-used feature. A tasteful implementer would make it do something reasonable by default, rather than making thousands of users click "Next" repeatedly and get presented with nonsensical defaults.
You might be vastly overestimating the correctness of files being imported.
Some coworkers of mine have to deal with CSV/TSV imports from enterprise customers, and the amount of clearly broken scripts is pretty bad.
That excel import preview dialog helps non-programmers try to fix these issues beforehand. If that wasn't there, it'd likely be impossible for these people to know where to begin trying to fix the import.
I usually just drag tab-sep files into an open Excel window, and it opens just fine. I only get the import wizard when I try to use file -> open.
There are a couple of "gotchas" I regularly experience- the worst of which is the automatic formatting- which unfortunately converts a number of gene names into dates (I'm in Bioinformatics). It's enough of an issue that papers have been published about it [1]. For example MAR1 ends up formatted as 1-Mar. When you have a list of 20,000 identifiers, it's quite annoying to deal with. I see the transformed strings show up in biological databases all the time. I don't know why there isn't an easy way to disable autoformatting. Even if I avoid incorporating Excel into my own workflow, when I send documents to scientists, they're going to want to use it, and we end up with the same results then.
My rage point recently- Why for the love of plain text can Excel not bother to encode csv exports as UTF-8? You can up and then download with google sheets to "hack" around this but I bought numbers.app out of spite since you can specify output encoding there.
There is RFC4180, but that came way after people were using it in lots or ways incompatible with the spec, so it isn't a huge help when paraing arbitrary files. I'd recommend following it if you're generating files though.
