[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pear-doc
Subject:    [Fwd: Re: [PEAR-DOC] cvs: peardoc /fr/package/database/db intro-dsn.xml
From:       81.57.128.152
Date:       2004-06-28 9:08:11
Message-ID: 20040628090845.47627.qmail () pb1 ! pair ! com
[Download RAW message or body]

didn't get to the list :|

["Re: [PEAR-DOC] cvs: peardoc /fr/package/database/db intro-dsn.xml intro-execute.xmlintro-fetch.xml" (message/rfc822)]

Message-ID: <40DFDE6F.9070501@keliglia.com>
Date: Mon, 28 Jun 2004 11:01:35 +0200
From: Mehdi Achour <didou@keliglia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030901 \
                Thunderbird/0.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Convissor <danielc@analysisandsolutions.com>
CC: Yannick TORRES <yannick.torres@keliglia.com>, 
 PEAR Doc List <pear-doc@lists.php.net>
Subject: Re: [PEAR-DOC] cvs: peardoc /fr/package/database/db intro-dsn.xml
 intro-execute.xml intro-fetch.xml
References: <cvsyannick1088354592@cvsserver> <20040627174842.GD15549@panix.com> \
                <200406272056.47665.yannick.torres@keliglia.com> \
                <20040627190742.GB3211@panix.com>
In-Reply-To: <20040627190742.GB3211@panix.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Dan,

Daniel Convissor wrote:
> On Sun, Jun 27, 2004 at 08:56:47PM +0200, Yannick TORRES wrote:
> 
> > On Sunday 27 June 2004 19:48, Daniel Convissor wrote:
> > 
> > > Here, and in several other places, you switched to using CDATA's where the
> > > en versions don't.  
> > 
> > Yes, and this declaration MUST be added to all examples in the documentation.
> 
> 
> 1) Where is that stated?

It's a rule for phpdoc-fr, Yannick just wanted to apply it here.

> 2) You're adding them unilaterally in one translation, where the original 
> and other translations don't.
> 
> If you feel they should be used, that's fine.  Start a discussion here on 
> the pear-doc list and we will talk about it.
> 
> Or, if you think there is one particular file in English that needs 
> updating, why not talk to the author of that file?

Ok, so let'st start a thread :)

Can one translation use specific things when needed ?

As for encoding the accents, you have to know that it's a pain in the 
ass to read a htmlencoded string. We were stuggling with the html 
entities in phpdoc-fr until Derick came up with a solution to fix this.
The french XML sources are now more user friendly, and we like to work 
on them :
   http://php.fr.doc.keliglia.com/revcheck.php?p=filesummary

I'll have a deeper look into this with Derick to see if he can do the 
same thing on peardoc. Is everyone okay with this ?

> > > Such modifications are likely to make long term 
> > > maintenance more difficult.

How ? I really don't get it here. We're slowly introducing the revcheck 
system in the french XML sources, this is how we're making the 
maintenance easyier. I don't think that having a CDATA in the french 
file, and not in the english file we'll be a huge problem.. just a 
specific language rules.

We're making efforts (see the fresh php.doc.web list) to group efforts
on the various php.net documentation. Our goal is to have translation 
teams, working on all documentations. We'll have per translations rules 
at the end, to ease the life of Mr FOO, phpdoc-XX translators who want 
to help with peardoc/XX without having to change his habits. And 
nowadays, knowing that it's possible to have plain accents in the XML 
sources, it's really a pita to still have to encode them for peardoc.

Yannick should have discussed this before starting his commits, but he's 
pretty new in the docs.. Let's forgive him :) He'll switch back to html 
encoded docs until we come with a common agreement. Yannick ? Au boulot !

Regards,

Mehdi Achour



-- 
PEAR Documentation List Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[prev in list] [next in list] [prev in thread] [next in thread]