Re: "Malformed XML" (l10n?) problems on checkout

--On February 16, 2005 10:44:17 PM -0600 kfogel@collab.net wrote:

> Charles Bailey <bailey@newman.upenn.edu> writes:
>> Two quick questions:
>> - Is it worth a small patch to xml.c to include the contents of the
>> offending buffer in a "Malformed XML" error message? It could yield a
>> long/multiline message, but would help identify the offending text in
>> a large operation.
>
> Hmmm. That's tough. How big can the buffer get? (It would do us no
> good to just display part of it, since we don't know where the problem
> characters would be.) We could have a heuristic that we display the
> buffer if it's below a certain size, and don't if it's above.
>
> Are you, um, volunteering? :-)

Sure. I just didn't want to take the time if there was already a
no-messages-longer-than-60-chars policy in place.

>> - Is it worth adding a bit of text about path name requirements to the
>> docs? Would it go in the Book (e.g. the UTF/Path requirements bit of
>> the developer info, or even a brief blurb about character sets in Ch
>> 1), or elsewhere?
>
> Yes, that patch would be uncontroversially welcome, I think!

OK, let me see if I can cons up a little sidebar on character sets for
somewhere in Ch 1 or 2 of the Book.

--
Regards,
Charles Bailey  < bailey _at_ newman _dot_ upenn _dot_ edu >
Newman Center at the University of Pennsylvania
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org