[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ossig] OpenOffice.org vs. M$ Office - migrationgotchas/issues?
short list of things to look out:
word doc using the following:
1. notes (those yellow post-it thingy)
2. change tracker (the things that track changes / deletion /
additions made to a document)
3. long table rows ( a row in a table that goes beyond 1 page)
4. content page (auto content page based on text headings)
5. outline numberings (e.g. 1. and 1.1)
those are the normal things that i had to redo / fiddle around with
when converting .doc. openoffice has these features, but the
conversion sometimes is sometime out.
the other thing is that, once you have used openoffice, converting
to .doc is a little bit more troublesome than the other way round.
anyway, welcome to the 'club'. there is an increasing number of small
business now using openoffice - because of the price and piracy
factors. plus the online community is quite good and forgiving.
Raja Iskandar Shah
----- Original Message -----
From: "Christopher DeMarco" <firstname.lastname@example.org>
Date: Thursday, July 1, 2004 8:59 am
Subject: [ossig] OpenOffice.org vs. M$ Office - migration gotchas/
> Hi all...
> I preface this discussion with two injunctions:
> 1. Thou shalt not flame.
> 2. Thou shalt not cheerlead, nor shalt thou troll.
> Ok, so that's really three. Whatever.
> I'm beginning to to evaluate whether and how to replace M$
> (hereinafter "M$") with OOo at my father's small law firm.
> planning and needs-assessements aside, I have some very
> questions about the potential speedbumps in featuresets
> interfaces. For example, most people make the highly subjective
> therefore highly varying observation that "advanced"
> properties do/do not migrate properly from one format to the
> I'm pretty ignorant about basic productivity-suite functionality
> use productivity-suites less than .001% of my computing time, and
> use about 1% of features) and have not closely analyzed OOo - so
> like to put the question to all of you: What
> non-compatibilities, feature mismatches and general fsckups are to
> found in a migration from M$ to OOo? More specifically:
> The featuresets in use vary greatly from org to org, but at a
> general level there are "show stoppers" in the feature
> between two different systems.
> What significant white spaces exist in feature-mappings between
> and M$? For example, XEmacs can't use XFT fonts and would
> significant hacking to implement them, whereas Kate does so
> Broadly, in strict terms of functionality, what can M$ do that
> can't? What M$ functionality does OOo implement, but so badly as
> impact usability?
> What significant incompatibilities exist between OOo and M
> Disregarding scripting issues and the potential for change in M
> file formats, are there any important document features which
> either impossible to import to OOo or which import wrongly?
> Since OOo obviously can't implement VB or any other M$
> technology (since it's a cross-platform app), document scripting
> is a
> big compatibility hurdle. Are there any conversion tools which
> port M$ scripts of varying triviality to the OOo (|| Python ||
> etc.) language?
> Another great concern is training - the user base will have to
> quickly brought to a level of productivity/comfort roughly
> to what they had with M$. What are the best existing resources
> training users to migrate M$ -> OOo? Imran's Mimos docs are
> what else out there is Ready For Primetime?
> Note that rules 1-2 leave you free to tell me to RTFM or STFW if
> asking obvious questions.
> ~ You are in a maze of twisty passages, all alike.
> Christopher DeMarco
> +6013 389 5658
> To unsubscribe: send mail to email@example.com
> with "unsubscribe ossig" in the body of the message
fn:Raja Iskandar Shah
org:RISC Niaga Enterprise;