Paul Pogonyshev <[EMAIL PROTECTED]> tapota :

> Mathieu Roy wrote:
>
>> > I may be willing to hunt for unclosed tags (like `<input ...>') etc.
>>
>> If you do, it may be more convenient that you directly commit your
>> bugfixes on the CVS. Are you interested?
>
> I wrote:
>
>> I prefer to have patched reviewed by experienced people in all cases.
>> But if you really think it is safe, you can give me write permission.
>> I will then only commit very simple patches, like this.  In case I
>> ever come up with anything more intelligent, I'll post it on the list
>> instead.
>
> However, you are probably right.  The changes are going to be very
> similar and boring.
>
> So far most frequent noticed error:
>
> * Non-closed tags (<input ...> instead of <input ... />.)
>
> * Upper-case tags and attributes (XML is case-sensitive, right?)
>
> * Wrong attribute name: <input maxlen="..." ... /> instead of
>   <input maxlength="..." ... />
>
> There are more, but I'd like to have it a little bit cleaned so that
> we can reduce the number of errors W3C checker prints to a reasonable
> number.
>
> How can I test pages with fixes applied?  Do I have to locally install
> Savane or are CVS sources systematically used at Gna!?

No, you have to perform a local install. Gna usually run a cvs
version, but only when we are confident enough with the current CVS.

Usually, development is made on branches. But as the changes you would
make would be only bugfix, these can be committed on the trunk
directly. 

Are you familiar with the short of savane/doc/devel? If so, you should
read it (it quite short).

Regards,

-- 
Mathieu Roy

  +---------------------------------------------------------------------+
  | General Homepage:           http://yeupou.coleumes.org/             |
  | Computing Homepage:         http://alberich.coleumes.org/           |
  | Not a native english speaker:                                       |
  |     http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english  |
  +---------------------------------------------------------------------+

Reply via email to