A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Word in Win7 vs. XP



 
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
  #1  
Old July 2nd 14, 07:23 PM posted to alt.windows7.general
Dick Baker[_2_]
external usenet poster
 
Posts: 22
Default Word in Win7 vs. XP

I have my new Win7 machine running alongside the old XP so I can move
into the new box with great care and deliberation.

Just found this bizarre difference in opening MS Word documents:

WordPad on XP will open *.doc files, but not the newer
*.docx files (which makes sense, since docx came along
much later.

WordPad on Win7 will open *.docx files, but NOT *.doc files.
Why in the world should that be?

--
--------------------------------------------
Dick Baker
(contact via http://goon.org/contact.php)
Ads
  #2  
Old July 2nd 14, 07:57 PM posted to alt.windows7.general
Philip Herlihy[_2_]
external usenet poster
 
Posts: 226
Default Word in Win7 vs. XP

In article ,
says...

On Wed, 02 Jul 2014 13:23:06 -0500, Dick Baker seesig4address wrote:

I have my new Win7 machine running alongside the old XP so I can move
into the new box with great care and deliberation.

Just found this bizarre difference in opening MS Word documents:

WordPad on XP will open *.doc files, but not the newer
*.docx files (which makes sense, since docx came along
much later.

WordPad on Win7 will open *.docx files, but NOT *.doc files.
Why in the world should that be?


I think there was an update for that. Wait for Windows Update to catch
up. You could try to search for the cure.


KenW


The trick is to right-click the document and pick "Open With...". Then
navigate in the interface to WordPad, open the file once with it, but
*don't* leave the "always..." box ticked. It'll remember the "Open
With" option, but will still open by default in Word (assuming you have
it installed).

Dunno where WordPad lives on W7, but it's at
"%ProgramFiles%\Windows NT\Accessories\wordpad.exe"
on my Vista box (my W7 laptop just croaked - grrrr).
You can get the location from the properties of a direct shortcut to
WordPad if you right-click that.

--

Phil, London
  #3  
Old July 2nd 14, 08:41 PM posted to alt.windows7.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default Word in Win7 vs. XP

Dick Baker wrote:

I have my new Win7 machine running alongside the old XP so I can move
into the new box with great care and deliberation.

Just found this bizarre difference in opening MS Word documents:

WordPad on XP will open *.doc files, but not the newer
*.docx files (which makes sense, since docx came along
much later.

WordPad on Win7 will open *.docx files, but NOT *.doc files.
Why in the world should that be?


I've been able to open .doc files using Wordpad (write.exe) back when I
was using Windows XP and now when I'm using Windows 7. Wordpad is
obviously not a replacement for Word so I will see a bunch of garbage
characters (formatting metadata) in the .doc file when viewed in Wordpad
but I can still see the content of the document.

"will not open" doesn't tell anyone what actually happens. You double-
click on a .doc file and nothing happens (no error message, you see
nothing show up on the screen)? You first load Wordpad and use its File
- Load menu to open a .doc file and nothing happens (no error message,
no change in the window for Wordpad)? You never see any error message?

What happens when you double-click on a .doc file from withing Windows
Explorer? If no handler is associated with that filetype, what happens
with you right-click on the .doc file and select Open With and then
navigate to %windir% to select write.exe to load and view the .doc file?
  #4  
Old July 2nd 14, 09:28 PM posted to alt.windows7.general
David E. Ross[_2_]
external usenet poster
 
Posts: 1,035
Default Word in Win7 vs. XP

On 7/2/2014 11:23 AM, Dick Baker wrote:
I have my new Win7 machine running alongside the old XP so I can move
into the new box with great care and deliberation.

Just found this bizarre difference in opening MS Word documents:

WordPad on XP will open *.doc files, but not the newer
*.docx files (which makes sense, since docx came along
much later.

WordPad on Win7 will open *.docx files, but NOT *.doc files.
Why in the world should that be?


Using Wordpad 6.1.7601.17514, which was installled with windows 7, I can
open old .doc files. However, the display in Wordpad shows all of the
file's content, including an attempt to resolve into text characters
those binary data that are used by Winword to indicate file properties,
formatting, and possibly history. This "garbage" is actually what I
would expect with Wordpad since it is indeed a tool for displaying the
entire contents of a file.

Do you have some version of Office on your PC? Or are you trying to get
by with only Wordpad because you do not have Winword? If the latter,
try the freeware Open Office from http://www.openoffice.org/, although
I have heard of some compatibility issues (which I no longer remember).

--
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See http://www.rossde.com/editorials/edtl_PutinUkraine.html.
  #5  
Old July 2nd 14, 09:47 PM posted to alt.windows7.general
Mike Easter
external usenet poster
 
Posts: 1,064
Default Word in Win7 vs. XP

Dick Baker wrote:

WordPad on XP will open *.doc files, but not the newer
*.docx files (which makes sense, since docx came along
much later.


XP WordPad will/would/ used to/ open MSWord 6.0/2003 compatible .doc
files. It won't save MSWord6 .doc.

WordPad on Win7 will open *.docx files, but NOT *.doc files.
Why in the world should that be?


Win7 WordPad will open OOXML .docx files (but MS rec/s Word Viewer).

WordPad stopped opening MSWord6 files in the Vista model. MSsaid that
there was a security vulnerability in addition to formatting problems.

http://support.microsoft.com/kb/960477 MS09-010: Vulnerability in
WordPad and Office text converters could allow remote code execution
https://technet.microsoft.com/library/security/ms09-010




--
Mike Easter
  #6  
Old July 2nd 14, 10:26 PM posted to alt.windows7.general
GS
external usenet poster
 
Posts: 68
Default Word in Win7 vs. XP

After serious thinking Dick Baker wrote :
I have my new Win7 machine running alongside the old XP so I can move
into the new box with great care and deliberation.

Just found this bizarre difference in opening MS Word documents:

WordPad on XP will open *.doc files, but not the newer
*.docx files (which makes sense, since docx came along
much later.

WordPad on Win7 will open *.docx files, but NOT *.doc files.
Why in the world should that be?


The release of write.exe that ships with Win7 is v6.X! The release that
shipped with XP was v5.x! The latter is not capable of opening MSO2007
and later because it doesn't understand the compound file structure
introduced with MSO12. The current release of write is written to
support the newer structure and any support for the older (outdated)
Word files has been deprecated.

That said, you could copy the older version of write.exe to your Win7
machine (not to a Windows folder) so you have both available, but this
involves also including the dependancy files since Wordpad is not a
stand-alone application!g Here's one (quite old) way...


http://www.computing.net/answers/win...d-1/12113.html

Optionally, you can use Open/Libre Writer or if not wanting an office
replacement there's several (free) Wordpad replacements available, of
which some are 'portable'!

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion



---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

  #7  
Old July 2nd 14, 10:33 PM posted to alt.windows7.general
Good Guy[_2_]
external usenet poster
 
Posts: 3,354
Default Word in Win7 vs. XP

On 02/07/2014 19:23, Dick Baker wrote:
I have my new Win7 machine running alongside the old XP so I can
move into the new box with great care and deliberation.

Just found this bizarre difference in opening MS Word documents:

WordPad on XP will open *.doc files, but not the newer *.docx files
(which makes sense, since docx came along much later.

WordPad on Win7 will open *.docx files, but NOT *.doc files. Why in
the world should that be?


You need to save the file as .rtf which can be opened in Wordpad. Also,
you can use free word on Microsoft cloud to read and convert your
documents. Finally, here are free converters that you can download from
microsoft website and they will open and read any Microsoft document
even in XP ;-)

Taking a rest from word cup football so you have this reply in rich text.

Good luck.




  #8  
Old July 3rd 14, 01:08 AM posted to alt.windows7.general
Mike Easter
external usenet poster
 
Posts: 1,064
Default Word in Win7 vs. XP

Good Guy wrote:
you have this reply in rich text.


What makes you think everyone (or even anyone) renders your html?

Everything after the f=f plaintext disappears (for me).

It seems that if your mixmin provider had their cleanfeed optimally
configured, html messages wouldn't make it.

http://www.mixmin.net/cleanfeed/config.html Cleanfeed - Configuration
Parameters

http://en.wikipedia.org/wiki/Cleanfe...et_spam_filter) As well as
blocking spam, it is also able to block binary image posts in non-binary
news groups and HTML posts.


--
Mike Easter
  #9  
Old July 3rd 14, 07:42 PM posted to alt.windows7.general
Dick Baker[_2_]
external usenet poster
 
Posts: 22
Default Word in Win7 vs. XP - OP follow-up

Dick Baker seesig4address wrote in news:XnsA35E7383B1581kx97@
216.196.97.131:

I have my new Win7 machine running alongside the old XP so I can move
into the new box with great care and deliberation.

Just found this bizarre difference in opening MS Word documents:

WordPad on XP will open *.doc files, but not the newer
*.docx files (which makes sense, since docx came along
much later.

WordPad on Win7 will open *.docx files, but NOT *.doc files.
Why in the world should that be?


My thanks to those who responded and apologies to all for (1) a horrible
typo, i.e., subject should have been WordPad in Win7 vs. XP, not just
Word (although you figured that out from the context) and (2) not being
clear by saying WordPad 6.0 in Win7 "will not" open older Word *.doc
files; it will open them, but displays binary code. Quite frankly, I
didn't scroll down far enough to discover that it was displaying the
original text after all the gibberish.




--
--------------------------------------------
Dick Baker
(contact via http://goon.org/contact.php)
  #10  
Old July 3rd 14, 08:36 PM posted to alt.windows7.general
Mayayana
external usenet poster
 
Posts: 6,438
Default Word in Win7 vs. XP - OP follow-up

| My thanks to those who responded and apologies to all for (1) a horrible
| typo, i.e., subject should have been WordPad in Win7 vs. XP, not just
| Word (although you figured that out from the context) and (2) not being
| clear by saying WordPad 6.0 in Win7 "will not" open older Word *.doc
| files; it will open them, but displays binary code. Quite frankly, I
| didn't scroll down far enough to discover that it was displaying the
| original text after all the gibberish.
|

In a sense that is "binary code". One can get that
in Notepad. It's not interpreting the .doc formatting
code. The text you see is not because Wordpad is
reading the file but because the actual text content
happens to be saved as standard ANSI characters.

If you don't get Wordpad to handle it and you don't
have Word, you might try the free Libre Office. It
handles all MS Office formats and converts between them.
(You can resave a docx as doc and vice versa, or as
PDF, HTML, etc.)

In case you or others might find it useful, I wrote
a script some time ago to handle DOCs. A lot of friends
and business contacts send DOCs because they're used
to MS Word. A short note might be turned into a relatively
giant file and then I need to wait for Libre Office to
load in order to read it. A few years ago MS made the
DOC format public, so now I just drop DOCs onto my
script and get a TXT file.

Paste the following text in Notepad and save as
DOCtoTXT.vbs. Drop a file onto it for conversion.
(Note: Security in Vista/7 may obstruct drag-drop
operation.)
Watch out for word wrap:

' begin script

Dim Arg, TFile, CBin, s2, A1, AText(), A2(1), A4(3), i2
Dim i3, LStart, LEnd, LLen, CR2, CrLf2, Ret, sErrStr, UB, Boo1, BooTog

On Error Resume Next

CR2 = vbCr & vbCr
CrLf2 = vbCrLf & vbCrLf

Arg = WScript.Arguments(0)
If Len(Arg) = 0 Then
MsgBox "This script works by dropping a .DOC file onto it.", 64,
"DOCtoTXT"
WScript.Quit
End If

If UCase(Right(Arg, 4)) ".DOC" Then
MsgBox "This script works by dropping a .DOC file onto it.", 64,
"DOCtoTXT"
WScript.Quit
End If

TFile = Left(Arg, (len(Arg) - 3)) & "txt" '-- path for text file.


Set CBin = New ClsBin
s2 = CBin.Read(Arg, 513, 32)

If (len(s2) = 0) Then
MsgBox "Error. File seems to be invalid.", 64, "DOCtoTXT"
Set CBin = Nothing
WScript.Quit
End If

A1 = CBin.GetArray(s2, False)

If (A1(0) 236) Or (A1(1) 165) Then
MsgBox "Error. DOC file header FIB section not found. This does not
seem to be a valid DOC file. Script cannot continue.", 64, "DOCtoTXT"
Set CBin = Nothing
WScript.Quit
End If

'-- Check fComplex flag.

A2(0) = A1(10)
A2(1) = A1(11)
i2 = CBin.GetNumFromBytes(A2)
If (i2 And 4) = 4 Then
MsgBox "This is a complex type DOC file. Script cannot continue.",
64, "DOCtoTXT"
Set CBin = Nothing
WScript.Quit
End If


'-- This could stand to have more error checking here. As it is, the code
'-- assumes that once the FIB marker is found the values for text offset,
text length, etc.
'-- will be valid.

'-- get text start and offset.
A4(0) = A1(24)
A4(1) = A1(25)
A4(2) = A1(26)
A4(3) = 0 '-- Text should not be over 65 KB from start of file, so just
skip this.
LStart = CBin.GetNumFromBytes(A4)

A4(0) = A1(28)
A4(1) = A1(29)
A4(2) = A1(30)
A4(3) = A1(31)
LEnd = CBin.GetNumFromBytes(A4)

LLen = (LEnd - LStart) '-- starting offset is LStart. LLen is bytes to
read.
s2 = CBin.Read(Arg, (LStart + 513), LLen) '-- add 1 to LStart because
CBin is 1-based. Also add 512 for FIB offset.

A1 = CBin.GetArray(s2, False)
UB = UBound(A1)
ReDim AText(UB + 1000) '-- won't need all this. just padding to be on
the safe side.
'-- s2 is now text of file. Fix it up and write to file.
i3 = 0
Boo1 = True '-- boolean to track whether to write file data.
BooTog = False '-- used to filter double vbCr.

'-- In addition to a number of characters that need to be dropped or
changed,
'-- "fields" need to be removed. This next section uses a tokenizing routine
'-- to walk the text string byte by byte. It's more work than a series of
replace
'-- functions, but it's more flexible. With tokenizing the fields can just
be
'-- dropped from the final text of the file.

For i2 = 0 to UB
If (Boo1 = False) Then
'-- Boo1 is set to false when Chr(19) is encountered, which
means the start of a field.
'-- 21 marks end of field... 21 marks start of field text.
Resume adding text to file.
'-- So this bit here is designed to skip the character if it's
in a field but toggle back to
'-- read for the next character once Chr(21) or 20 is found.
If (A1(i2) = 21) Or (A1(i2) = 20) Then Boo1 = True
Else
Select Case A1(i2)
Case 19
Boo1 = False '-- marks beginning of field. drop out
following text.
Case 11, 12
AText(i3) = 13
AText(i3 + 1) = 10
i3 = i3 + 2
Case 13
If BooTog = True Then
BooTog = False '-- skip 2nd vbCr in series.
Else '-- Chr(13) is end of paragraph, so convert it to
vbCrLf & vbCrLf.
'-- but Chr(13) also often comes in pairs, which
ends up leaving too much space.
'-- so convert any Chr(13) found but skip the
2nd if there are two together.
AText(i3) = 13
AText(i3 + 1) = 10
AText(i3 + 2) = 13
AText(i3 + 3) = 10
i3 = i3 + 4
BooTog = True
End If
Case 0, 1, 2, 3, 4, 5, 6, 7, 8, 14, 20, 21
'-- nothing. drop these out.
Case 30, 31, 45
AText(i3) = 45
i3 = i3 + 1
Case 145 ' apostrophe fix where Word puts a single opening
quote mark.
AText(i3) = 39
i3 = i3 + 1
Case Else
AText(i3) = A1(i2)
i3 = i3 + 1
End Select
End If
'-- un-toggle 2nd vbCr trap if this was not a vbCr
If (A1(i2) 13) Then BooTog = False
Next

ReDim Preserve AText(i3 - 1)

Ret = CBin.WriteFileA(TFile, AText, True)
If (Ret 0) Then
MsgBox "Error " & CStr(Ret) & ". " & sErrStr, 64, "DOCtoTXT"
Else
MsgBox "Text version saved as" & vbCrLf & TFile & ".", 64, "DOCtoTXT"
End If

Set CBin = Nothing
WScript.Quit

Class ClsBin
Private FSO, i, TS, sAst, ANums, Char1

Private Sub Class_Initialize()
sAst = "*"
Char1 = Chr(1)
Set FSO = CreateObject("Scripting.FileSystemObject")
End Sub

Private Sub Class_Terminate()
Set TS = Nothing '-- just in case.
Set FSO = Nothing
End Sub

'----------------- size =
GetSize(FilePath) ---------------------------------------------------------
'-- get size of file in bytes. returns -1 if file
not found.
Public Function GetSize(sFilePath)
Dim OFil
If (FSO.FileExists(sFilePath) = False) Then
GetSize = -1
Exit Function
End If
Set OFil = FSO.GetFile(sFilePath)
GetSize = OFil.Size
Set OFil = Nothing
End Function

'-- This is just a wrapper for TexStream.Read function, to simplify things
'-- and avoid needing to deal with TS and FSO details repeatedly.
'-- note that ReadAll does not return a usable string. This function always
uses Textstream.Read.
'--------------------------------- s = Read(FilePath, StartPoint,
Length) ------------------------------------
Public Function Read(sFilePath, StartPt, LenR)
Dim LenF
On Error Resume Next
Read = ""
If (FSO.FileExists(sFilePath) = False) Then Exit Function
LenF = GetSize(sFilePath)
If (StartPt = LenF) Then Exit Function '-- if startpoint is beyond
end of file then quit.
'-- if request
is to Read beyond end of file then just Read to end and return that.
If (StartPt 1) Then StartPt = 1 '-- adjust in case 0 was sent
for start point.
If (LenR = 0) Then LenR = LenF '-- send 0 in 3rd parameter to
Read entire file.
Set TS = FSO.OpenTextFile(sFilePath, 1)
If (StartPt 1) Then TS.Skip (StartPt - 1)
Read = TS.Read(LenR)
TS.Close
Set TS = Nothing
End Function

'---------------- Write a file. -------
Public Function WriteFileA(sFilePath, ArrayIn, OverWrite)
Dim sA1, iA1
On Error Resume Next
If (FSO.FileExists(sFilePath) = True) Then
If (OverWrite = True) Then
FSO.DeleteFile sFilePath, True
Else
WriteFileA = 1 '-- file exists.
Exit Function
End If
End If
If IsArray(ArrayIn) = False Then
WriteFileA = 2 '-- ArrayIn value is not an array.
Exit Function
End If
Err.Clear
For iA1 = 0 to UBound(ArrayIn)
ArrayIn(iA1) = Chr(ArrayIn(iA1))
Next
sA1 = Join(ArrayIn, "")

Set TS = FSO.CreateTextFile(sFilePath, True)
TS.Write sA1
TS.Close
Set TS = Nothing
'-- return 0 if no errors.
WriteFileA = Err.Number
If (Err.number 0) Then sErrStr = Err.Description
End Function

'-- returns an array of byte values from
'-- a string. This is a way to leave the 0-bytes alone
'-- while still being able to Read numeric
'-- values from the bytes.
Function GetArray(sStr, SnipUnicode)
Dim iA, Len1, Len2, AStr()
On Error Resume Next
Len1 = Len(sStr)
If (SnipUnicode = True) Then
ReDim AStr((Len1 \ 2) - 1)
Else
ReDim AStr(Len1 - 1)
End If

If (SnipUnicode = True) Then
For iA = 1 to Len1 step 2
AStr(iA - 1) = Asc(Mid(sStr, iA, 1))
Next
Else
For iA = 1 to Len1
AStr(iA - 1) = Asc(Mid(sStr, iA, 1))
Next
End If
GetArray = AStr
End Function
'--- return a number from 2 or 4 bytes.
Public Function GetNumFromBytes(AIn)
Dim Num1
On Error Resume Next
Select Case UBound(AIn)
Case 1
Num1 = AIn(0) + (AIn(1) * 256)
Case 3
Num1 = AIn(0) + (AIn(1) * 256)
Num1 = Num1 + (AIn(2) * 65536)
Num1 = Num1 + (AIn(3) * 16777216)
Case Else
Num1 = 0
End Select
If (Err.number = 0) Then
GetNumFromBytes = Num1
Else
GetNumFromBytes = -1
End If
End Function

End Class

'end script


  #11  
Old July 3rd 14, 09:38 PM posted to alt.windows7.general
Good Guy[_2_]
external usenet poster
 
Posts: 3,354
Default Word in Win7 vs. XP

On 03/07/2014 01:08, Mike Easter wrote:


What makes you think everyone (or even anyone) renders your html?


Intelligence of the people I guess. Most intelligent people in the 21st
century must be accustomed to HTML in the corporate emails as a matter
of course. We don't get many hunters and fishermen around here.



Everything after the f=f plaintext disappears (for me).


In that case you need to get a better newsreader.



It seems that if your mixmin provider had their cleanfeed optimally
configured, html messages wouldn't make it.

http://www.mixmin.net/cleanfeed/config.html Cleanfeed -
Configuration Parameters

http://en.wikipedia.org/wiki/Cleanfe...et_spam_filter) As well
as blocking spam, it is also able to block binary image posts in
non-binary news groups and HTML posts.



What has the above crap got to do with me? I can't do anything about it
if mixmin can't configure their servers optimally.

HTML is what people will get. If they are on a narrow bandwidth then
they have to learn how to kill-file my posts. Perhaps you can write a
tutorial for these people.



  #12  
Old July 3rd 14, 10:46 PM posted to alt.windows7.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default Word in Win7 vs. XP

GS wrote:

Dick Baker wrote :

I have my new Win7 machine running alongside the old XP so I can move
into the new box with great care and deliberation. Just found this
bizarre difference in opening MS Word documents:

- WordPad on XP will open *.doc files, but not the newer *.docx files
which makes sense, since docx came along much later.

- WordPad on Win7 will open *.docx files, but NOT *.doc files.

Why in the world should that be?


The release of write.exe that ships with Win7 is v6.X! The release that
shipped with XP was v5.x! The latter is not capable of opening MSO2007
and later because it doesn't understand the compound file structure
introduced with MSO12. The current release of write is written to
support the newer structure and any support for the older (outdated)
Word files has been deprecated.

That said, you could copy the older version of write.exe to your Win7
machine (not to a Windows folder) so you have both available, but this
involves also including the dependancy files since Wordpad is not a
stand-alone application!g Here's one (quite old) way...


http://www.computing.net/answers/win...d-1/12113.html

Optionally, you can use Open/Libre Writer or if not wanting an office
replacement there's several (free) Wordpad replacements available, of
which some are 'portable'!


And to add further to that suggestion:

With all the free and more robust choices for Word alternatives, I
wouldn't recommend the hacked solution of copying write.exe from the
Windows XP host to the Windows 7 host.

Getting MS Word is one option (although most users that choose that
route would get MS Office instead of just the standalone Word
component). That's a pricey option. Buying a used computer (that's
broke, like a hard drive needs replacing) that had an OEM version of MS
Office installed would be cheaper than buying MS Office alone. Friends
that buy a new computer (they want something new and more powerful or
their old one broke), using Craigslist, or finding a local scrapper are
choice. If the box still has a legible OEM sticker, I can download the
installers for free from Microsoft and use that product key. After all,
the OEM license permanently sticks to the computer and now I have that
computer.

As you mentioned, another would be to get LibreOffice (which is a more
actively maintained product than OpenOffice that got dumped at the
Apache Software Foundation). It's free but it's still slow to open
(faster than before but still slow compared to Word or the other
solutions mentioned here). It has a wonderful robust set of features
(mostly to replicate what MS Office can do although sometimes the
workarounds to effect the same task are very non-intuitive in Libre or
OpenOffice). It's a heavy-weight solution.

Another choice is to get software that emulates MS Office but is free or
very cheap, like Kingsoft Office Suite or Softmaker's FreeOffice. Those
don't have every feature in MS Office or LibreOffice but then most users
only utilize less than half of the features in the heavy-weight suites.
You have to dig or be an existing user of some esoteric features to find
them missing in these smaller and quick office tools. Both have
freeware versions. There isn't much lure users into buying the payware
version of Kingsoft because almost everything is already in the freeware
version. FreeOffice does have a few nice features that even home users
might want to lure them to the payware version. Both are much cheaper
than buying just one component of MS Office: free for Kingsoft Office or
$70 for Kingsoft Pro, and free for Softmaker FreeOffice or $100 for
Softmaker Office pro. Unless you have a real need for the extra
features in the payware versions, the freeware versions are a very good
alternative to MS Office. However, no matter if you use the free or
paid versions, they don't include a PIM with e-mail product as Microsoft
does with Outlook in some [more pricey] editions of MS Office.

The OP never said he needs to edit the files so getting MS Word Viewer
(and the other MS Office component viewers) is another option. All he
said is that he wants to "open" them (which only means to read them).
Because they are not full-blown versions of the Word, Excel, and other
MS Office components, some .doc[x] files may not display with 100%
fidelity. After all, these are just small free viewer apps. If only
viewing (reading) the doc files is all the OP wants then these free
viewers from Microsoft are sufficient.

There are probably other cheaper solutions (many free) than getting MS
Office and more lightweight solutions than LibreOffice. What to use
depends on what he wants to do with the doc files and his level of
expertise in whatever Word features he needs or wants to use.
  #13  
Old July 4th 14, 12:41 AM posted to alt.windows7.general
David E. Ross[_2_]
external usenet poster
 
Posts: 1,035
Default Word in Win7 vs. XP

On 7/3/2014 1:38 PM, Good Guy wrote:
On 03/07/2014 01:08, Mike Easter wrote:


What makes you think everyone (or even anyone) renders your html?


Intelligence of the people I guess. Most intelligent people in the 21st
century must be accustomed to HTML in the corporate emails as a matter
of course. We don't get many hunters and fishermen around here.



Everything after the f=f plaintext disappears (for me).


In that case you need to get a better newsreader.



It seems that if your mixmin provider had their cleanfeed optimally
configured, html messages wouldn't make it.

http://www.mixmin.net/cleanfeed/config.html Cleanfeed -
Configuration Parameters

http://en.wikipedia.org/wiki/Cleanfe...et_spam_filter) As well
as blocking spam, it is also able to block binary image posts in
non-binary news groups and HTML posts.



What has the above crap got to do with me? I can't do anything about it
if mixmin can't configure their servers optimally.

HTML is what people will get. If they are on a narrow bandwidth then
they have to learn how to kill-file my posts. Perhaps you can write a
tutorial for these people.



Problems with HTML-formatted E-mail and newsgroup messages, from my own
research:

1. Many E-mail and newsgroup applications generate really bad HTML.
HTML-formatted messages contain an average of 5.0 HTML syntax errors per
KB of file size. That is okay if you and I both use the same
application. It is not okay if we use different applications.

2. Because of HTML syntax errors, the message might not be processed by
audio applications used by the deaf. For businesses in the U.S., this
can be a legal problem, a violation of the Americans with Disabilities
Act. If you think I am kidding, ask the Target Corporation what
happened in 2007-2008.

3. HTML-formatted messages average 4.0 times the size of the equivalent
ASCII-formatted WITH THE SAME CONTENT. This is called bloat and is a
problem for corporations that are mandated by law to retain all
corporate E-mail messages.

--
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See http://www.rossde.com/editorials/edtl_PutinUkraine.html.
  #14  
Old July 4th 14, 02:12 AM posted to alt.windows7.general
Char Jackson
external usenet poster
 
Posts: 10,449
Default Word in Win7 vs. XP

On Thu, 03 Jul 2014 21:38:08 +0100, Good Guy
wrote:

On 03/07/2014 01:08, Mike Easter wrote:


What makes you think everyone (or even anyone) renders your html?


Intelligence of the people I guess. Most intelligent people in the 21st
century must be accustomed to HTML in the corporate emails as a matter
of course. We don't get many hunters and fishermen around here.



Everything after the f=f plaintext disappears (for me).


In that case you need to get a better newsreader.



It seems that if your mixmin provider had their cleanfeed optimally
configured, html messages wouldn't make it.

http://www.mixmin.net/cleanfeed/config.html Cleanfeed -
Configuration Parameters

http://en.wikipedia.org/wiki/Cleanfe...et_spam_filter) As well
as blocking spam, it is also able to block binary image posts in
non-binary news groups and HTML posts.



What has the above crap got to do with me? I can't do anything about it
if mixmin can't configure their servers optimally.

HTML is what people will get. If they are on a narrow bandwidth then
they have to learn how to kill-file my posts. Perhaps you can write a
tutorial for these people.


It's hard to take a person seriously after they've publicly declared that
they'll continue to use this newsgroup as their personal toilet.

--

Char Jackson
  #15  
Old July 4th 14, 02:35 AM posted to alt.windows7.general
GS
external usenet poster
 
Posts: 68
Default Word in Win7 vs. XP

Extremely well stated! I completely forgot about the viewer apps,
though, and so thanks for mentioning.

I'm an Excel developer and so having MSO's current version to work with
is not optional. I typically install Word because clients insist on
using it, otherwise I haven't found anything Word does that I can't
duplicate in Excel. Exception is using Adobe's RoboHTML for output to
PDF but I try to avoid that since Excel's SaveAsFixedFormat feature
does a great job without the 'weight' associated with other methods for
creating Xps/Pdf files. I can always add the nav panel later!

I knew about FreeOffice but your post is 1st I've heard Kingsoft.

I didn't know about OEM downloads being available and so would
appreciate any refs you can give about source.

Big thanks...

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion


 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 07:59 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.