...Jim Thompson
--
| James E.Thompson, P.E. | mens |
| Analog Innovations, Inc. | et |
| Analog/Mixed-Signal ASIC's and Discrete Systems | manus |
| Phoenix, Arizona Voice:(480)460-2350 | |
| E-mail Address at Website Fax:(480)460-2142 | Brass Rat |
| http://www.analog-innovations.com | 1962 |
I love to cook with wine. Sometimes I even put it in the food.
A quick Google search yeilds:
http://visioo-writer.tuxfamily.org/EN/
No garuantees -- I haven't tried it since I use the full-up version of
OpenOffice!
Stuart
Magnifico!! Thanks! Works great!
Install the whole thing. It works much better than the Microslop
alternative. Further, it is much more compatible with earlier versions
of Microslop's word files than the latest version of Microslop word.
-Chuck
I only use "earlier versions of Microslop's" ;-)
And the VisiOO-Writer suggestion from Stuart Brorson works
delightfully, well written, and compact.
> Is there an OpenOffice file viewer available? I'd rather not have to
> install the full product.
What kind of file are you trying to view? What OS? OpenOffice is able
to deal with a variety of file formats, as far as I know.
Good Luck!
Rich
A "contestant", who shall remain nameless, sent a submission as *.sxw
I am Micro$oft-based, but Brorson's VisiOO solution works perfectly.
I recently installed Micro$oft word 2003. Couldn't read half of my own
files anymore. Had to change fonts etc everywhere. Seems Word isn't
compatible with Word.
When I must choose I use OpenOffice. I installed both, I need to read
and change files others send to me, so I have to. It is possible with
OpenOffice, but that may give incompatibilityproblems.
Pieter
>I recently installed Micro$oft word 2003. Couldn't read half of my own
>files anymore. Had to change fonts etc everywhere. Seems Word isn't
>compatible with Word.
That's odd: I didn't have any trouble, and some of my documents were
converted long ago from WordPerfect for Windows 3. Maybe you had some
fonts that weren't of a compatible format.
--
Regards, John Woodgate, OOO - Own Opinions Only.
If everything has been designed, a god designed evolution by natural selection.
http://www.jmwa.demon.co.uk Also see http://www.isce.org.uk
Ah, c'mon. You had to know it was the OpenDocument format
(that M$ will NEVER support).
Microsoft Lashes out at Massachusetts IT Decision
http://slashdot.org/article.pl?sid=05/09/03/2214219&mode=nocomment
Wait--I may have spoken too soon:
Massachusetts Finalizes OpenDocument Standard Plan
http://slashdot.org/article.pl?sid=05/09/24/1317234&mode=nocomment
Hmm. I use OOo exclusively, but if I send something out it goes as a
pdf file. If the customer is going to want to edit the thing then I
inquire, which usually leads to the file getting sent in MS Office
compatible format.
--
Tim Wescott
Wescott Design Services
http://www.wescottdesign.com
>I read in alt.binaries.schematics.electronic that Pi
><ditb...@bigfoot.com> wrote (in
><2j7jj11aqgn1a8spn...@4ax.com>) about 'OT: OpenOffice
>Viewer ??', on Tue, 27 Sep 2005:
>
>>I recently installed Micro$oft word 2003. Couldn't read half of my own
>>files anymore. Had to change fonts etc everywhere. Seems Word isn't
>>compatible with Word.
>
>That's odd: I didn't have any trouble, and some of my documents were
>converted long ago from WordPerfect for Windows 3. Maybe you had some
>fonts that weren't of a compatible format.
I checked: in the original Word2000 it was CG Times, and that doc was
created on another computer. When I open it in Word 2003 on this
computer, that font is not in the list. And Word2003 displays that
even can't be recognized as font, looks very strange. So I probably
used a font that is not on this computer. Word should have saved the
font in the document, the possibility is there but is standard off.
Making Word docs incompatible with those on other computers.
You can't expect me to instruct everybody to use only certain fonts.
Or to instruct them to change those settings, or keep a list of
allowed fonts near the computer.
Every time when I get a new computer I must change settings everywhere
to be able to work ok. That should not be necessary. It should be plug
and play. Install and run, not a whole week of installing all
programs, changing setings (and remember all settings in all software
you have to change), install firewalls, virusscanners, ad-ware
killers, spamfilters, change whole windows to get rid of those
balloons, eror messages etc etc etc
Pieter
>>What kind of file are you trying to view?
>>OpenOffice is able to deal with a variety of file formats
>> Rich Grise
>
> Ah, c'mon. You had to know it was the OpenDocument format
> (that M$ will NEVER support).
> Microsoft Lashes out at Massachusetts IT Decision
> http://slashdot.org/article.pl?sid=05/09/03/2214219&mode=nocomment
Heh. They sound just like Republicans. ;-P
Cheers!
Rich
A Progressive sees a glass half full of of water and says,
"We need to find a way to fill up the glass".
A NeoCon sees a glass half full of of water and says,
"Hey! Who drank half of my water".
And some engineers would point out that the glass is over designed by a
factor of two as a safety measure.
--
--
kens...@rahul.net forging knowledge
<snip>
>
>Every time when I get a new computer I must change settings everywhere
>to be able to work ok. That should not be necessary. It should be plug
>and play. Install and run, not a whole week of installing all
Why should it be?? Everytime I buy a TV or DVD player, should it be
exactly the same remote. Welcome to the real world. Every one is quick
to blame the PC, but I bet the products you design are the same.
And a real engineer would say what a waste of space (and water), that
could be filled with beer.
Cheers!
Rich
But I do not have to spend a whole week programming the remote.
And I design my electronics and software in such way that people
should not have to read a manual!
Pieter
*.sxw is apparently an archive method of collecting a "project". At
any rate the VisiOO viewer works just ducky and it's only about 3MB.
> *.sxw is apparently an archive method of collecting a "project". At
> any rate the VisiOO viewer works just ducky and it's only about 3MB.
>
>
...Jim Thompson
*.sxw is simply staroffices xml wordprocessor file.
Open office started its life as a german product. The german company was
bought up by Sun microsystems. Sun initially sold the package as Star Office,
and quickly found that they couldn't make a foothold in microslop's market,
so they started giving the package away for free to anyone that wanted it.
After doing that for a couple of years, they released the package to open source,
(much like Netscape, and Mozilla) and open office.org was born.
-Chuck
: *.sxw is apparently an archive method of collecting a "project". At
: any rate the VisiOO viewer works just ducky and it's only about 3MB.
Nein, mein Herr! .sxw is the OpenOffice document processor's
file extension. It is analogous to Microsoft Word's .doc extension.
There may be some collision between OpenOffice's and somebody else's
definition of the .sxw file extension, which is why it shows up as a
"project collection" to you.
To answer the implied question -- "what does .sxw stand for?" -- I
have no idea. Perhaps "Star [1] (something) word"? FWIW, the
OpenOffice spreadsheet file extension is .sxc, and the OpenOffice
PowerPoint equivalent has file extension .sxi. I see a pattern
forming here . . . .
Stuart
[1] As Chuck pointed out, OpenOffice started its life as a commerical
office package for Linux called StarOffice.
*.ODT is OpenDocument Text (XML).
I am not sure if it is compressed.
I do know that the OpenDocument data in a *.SXW
has been run thru a compression algorithm
before it is written to the disk.
You are both correct.
>In sci.electronics.cad Jim Thompson <thegr...@example.com> wrote:
My surfing around says *.XML is equivalent to M$oft's *.DOC, but *.SXW
IS an archive that you can open with WinZip and see a bunch of XML
files plus whatever graphic files were used.
If you open an SXW file with VisiOO Viewer it's something like
Publisher, you SEE a document including graphics.
I stumbled onto that. Opened the SXW file with WinZip and could see
XML files plus PNG graphic files.
The image file extension is .SXD.
Star (placeholder) Draw.
There's also
*.SXM Math File
*.SXP Presentation
When the database manager comes out of beta,
it will be using *.SXB.
Star (placeholder) Base.
>>
>> [1] As Chuck pointed out, OpenOffice started its life as a commerical
>> office package for Linux called StarOffice.
>
> My surfing around says *.XML is equivalent to M$oft's *.DOC, but *.SXW
> IS an archive that you can open with WinZip and see a bunch of XML
> files plus whatever graphic files were used.
>
> If you open an SXW file with VisiOO Viewer it's something like
> Publisher, you SEE a document including graphics.
>
> ...Jim Thompson
I can confirm that. Open office tries to be conservative with space, and
it is also bound to be open with its file formats. As a result, they use
zip to compress the plain text/graphics structure that forms the document.
Word, on the other hand is a closed format, and microslop won't tell you the
format for any reason. The are in the process of patenting bits and pieces
of the file formats of their various office utilities. You can guess the
reason! Their attitude is why one of those states in the uppa-u-ass decided
to insist that all their state documents be in the Open office format.
Microslop has been begging for this kind of action for the longest time. They
have finaly pissed off enough people that it is going to happen.
-Chuck
Kewl! Thanks for the explanation! Makes sense to me!
Stuart
.sxw (and probably .odt as well) files are actually .tar.gz files, with
the tarball containing a directory of other files - the main word
processor document (in xml format) and any required binary files
(pictures, fonts, etc.).
--
Regards,
BruceR
data2docSAFE at URLfastmail.com.au (Please modify to reply)
: If you open an SXW file with VisiOO Viewer it's something like
: Publisher, you SEE a document including graphics.
Indeedy. A colleague had a word doc containing images that he wanted as
seperate items. Read the doc into openoffice.org and saved in swx format.
He unzipped the .swx and there were images as jpg's neatly available for
him!