> I tried it on some piece of LCLProc. I ran into the following when I tried
> to commit
> the result to svn:
> WriteXMLFile(doc, FDocFileName) creates a new xml file. Multiline
Strange, it should work on the exisiting LCLProc.xml, as it checks if the
file exists or not. I believe that if it creates a new file the file will
be corrupt for FPDoc.
> Maybe the XMLWrite unit should generate line-endings that are conformant
> to the OS
> it is running on. Or does the XML-specification dictate unix line-endings?
Seems that it's XML specification:
2.11 End-of-Line Handling
XML parsed entities are often stored in computer files which, for editing
convenience, are organized into lines. These lines are typically separated
by some combination of the characters CARRIAGE RETURN (#xD) and LINE FEED
(#xA).
To simplify the tasks of applications, the XML processor MUST behave as if
it normalized all line breaks in external parsed entities (including the
document entity) on input, before parsing, by translating both the
two-character sequence #xD #xA and any #xD that is not followed by #xA to
a single #xA character.
Dunno yet how to fix this...
> The question is: can we use packages to install add-ins (or plug-ins) into
> the IDE?
> Then we can offer this dialog as a plug-in package that people can install
> (and we
> don't need $IFDEF in lazarus itself).
True, but it's been ifdef'ed because it's stil a prototype. As soon as
it's stable and working correct that you can lose the ifdefs. I believe
that the LazDoc should be considered as an intrinsic part of Lazarus.
On the other hand I agree that you CAN distribute it as an add-on. But
this applies to more stuff under tools, like diff amongst others.
You're right about the wiki page (didn't think of it). I will add a page
on lazdoc there in good time.
Darius
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
