On Mon, 28 Nov 2005 03:40, mark wrote:
Daniel Carrera wrote:
Wesley Parish wrote:
I suspect Microsoft dragged over some of their programming gurus from
arcane C/C++-using projects to draft this standard, because it's got
snip
Arcane? Uh, you mean like OpenOffice.org's codebase? Or all of
Wesley Parish wrote:
I suspect Microsoft dragged over some of their programming gurus from arcane
C/C++-using projects to draft this standard, because it's got the feeling of
the Microsoft Standard variable-naming procedures that I've seen discussed in
various programming magazines here and
Daniel Carrera wrote:
Wesley Parish wrote:
I suspect Microsoft dragged over some of their programming gurus from
arcane C/C++-using projects to draft this standard, because it's got
snip
Arcane? Uh, you mean like OpenOffice.org's codebase? Or all of Linux?
Or Firefox?
mark yes, I
2005/11/26, Daniel Carrera [EMAIL PROTECTED]:
Of course it can be abreviated. What I'm saying is that abreviating it
is not going to give you the benefit that you think it will. It will not
speed up parsin, it will not make the file load faster. It will save
disk space, but I doubt that disk
Henrik Sundberg wrote:
I'd say that smaller files are faster than bigger.
The slow down due to the size increase is infinitesimal. See below for
an example. It's like arguing that you should use small variables in
your python program because that will make the file faster. Anyone who
knows
Randomthots wrote:
1. Does Microsoft's XML standard now encompass all document types? Last
I knew they only had an XML format for Word.
Microsoft's FAQ says:
Currently, only Microsoft Office Word, Microsoft Office Excel, and
Microsoft Office PowerPoint will use Office XML Formats
In
Daniel Carrera wrote:
I haven't yet seen any examples of the new Excel format. But verbosity
isn't really an issue.
snip
The number of characters has no effect on speed. There is no reason why
w:r is faster to parse than text:span text:style-name=T1.
I'm sorry, Daniel, but I find that
Daniel Carrera wrote:
Randomthots wrote:
The number of characters has no effect on speed. There is no reason
why w:r is faster to parse than text:span text:style-name=T1.
I'm sorry, Daniel, but I find that hard to believe.
I have a file that is strictly text, numbers, and dates. Seven
Daniel Carrera wrote:
Hi all,
Excellent article at Groklaw:
http://www.groklaw.net/article.php?story=20051125144611543
It's a technical comparison between OpenDocument and Microsoft's XML
format. It's intended to be suitable for a semi-technical audience (ie.
people who know a bit of HTML)