> But I think it's not so easy.. I mean.. Translators file is update when
> someone run a cvs commit or every day at manual build?
See the way NEWS works on the source-tree. Every day, a cron-job updates the
NEWS file (with cvs-id of 'changelog'), and the mail-the-commits-program is
programmed to
> > > Revision tags in the translated or the original English XML files are
> > > nonsense. Every translator have to look into the phpdoc tree at
> > > cvs.php.net.
> >
> > WHHYYY?
>
> You cannot do a translation with revison tags. So it is nonsense. You can
> not make a diff
On Thu, Aug 09, 2001 at 08:06:35PM +0200, Hojtsy Gabor wrote:
> Egon writes:
>
> > Revision tags in the translated or the original English XML files are
> > nonsense. Every translator have to look into the phpdoc tree at
> > cvs.php.net.
>
> WHHYYY?
You cannot do a translati
Egon writes:
> Revision tags in the translated or the original English XML files are
> nonsense. Every translator have to look into the phpdoc tree at
> cvs.php.net.
WHHYYY?
Goba
Ciao Goba,
> > on this way we don't need to grep every file
> > ... but only some temp file.
>
> Here we do not want to optimize the grep, but
> would like to optimize our work. Placing tha revision
you're right.. :)
> inside the file, means:
>
> - one commit (one modification to only one f
On Thu, Aug 09, 2001 at 12:08:32AM +0200, Thomas Schöfbeck wrote:
> Sounds also good!
>
> Let's summarize:
>
> is already available,
>
> is OK for Jeroen, Goba, Luca, and me (=3 1/2)
>
>
> is at least for me also OK,
> since the "State" saves the manipulation of translators when
> committi
Hojtsy Gabor wrote:
> > > > Is
> > > >
> > Right.. or like I've already said
> >
> >
> > Directory/File Translator Status/EN
> > =
> > bookinfo.xml perugini T1.13
> >
> >
> >
> > > >
> >
> > We can use
> > //CVS/Entries
> >
> >
> > on
Hi Luca,
Thanks for the offer from your last posting!
As Goba already explained, we should check on the translation-side the
comment in the file ().
Even the is really useful for the
working-copies,
(as also very good explained by Goba :), I think that it doesn't matter
if we
check against the
> Is
>
> a good idea? It is (on purpose) very similar to:
>
Great!
> > > Is
> > >
> Right.. or like I've already said
>
>
> Directory/File Translator Status/EN
> =
> bookinfo.xml perugini T1.13
>
>
>
> > >
>
> We can use
> //CVS/Entries
>
>
> on this way we don't need to grep every file
> ... b
> > Is
> >
Right.. or like I've already said
Directory/File Translator Status/EN
=
bookinfo.xmlperuginiT1.13
> >
We can use
//CVS/Entries
on this way we don't need to grep every file
... but onl
> Is
>
> a good idea? It is (on purpose) very similar to:
>
Right.
Goba
> thanks you for this proposal, your d-param is what I meant, but only
> from within the file (That saves sometimes a second commit, and has
> other advantages).
>
> But it shows, that others are also working on this issue.
Noone came up with a script, just Luca :)) The things are
OK here, but w
Ciao Thomas,
what you mean is something like a report for a particular module?
eg.:
./checkTr d it/function/mysql.xml
I'd like to share my effort with you and other in a common solution.
I think what was done by Simone, add a revision en number on
it/Translators, it's a good start point.
> But it shows, that others are also working on this issue.
>
> Maybe we should really try to agree on a common solution for this?
I agree with Thomas. I'm sure that with some cooperation a nice
solution can be reached.
> Exactly that's the the wrong way. If the change in May 2000 was only a
typ
Hi Luca,
thanks you for this proposal, your d-param is what I meant, but only
from within the file (That saves sometimes a second commit, and has
other advantages).
But it shows, that others are also working on this issue.
Maybe we should really try to agree on a common solution for this?
Cu,
Hojtsy Gabor wrote:
> > No. One revision is not enough. We need the revision history and that
> > should no be in the documentation. Your way is also possible, but to what
> > revision?
>
> How is the revision history is useful?? Why a simple revision
> number is not enough? OK, lets draw a tab
[EMAIL PROTECTED] wrote:
> On Tue, Aug 07, 2001 at 04:55:14PM +0200, Hojtsy Gábor wrote:
> > >> So we have a $Revision tag in the english file, showing the actual
> > >> english version number. We can have a comment in the translated
> > >> version, about what english version number it correspo
[EMAIL PROTECTED] wrote:
> On Tue, Aug 07, 2001 at 11:39:53AM +0200, Thomas wrote:
> > [EMAIL PROTECTED] wrote:
> >
> > > On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote:
> > > > Hojtsy gábor wrote:
> > >
> > > > > >>I too think that this is not needed for translations. I can't think
> > >
> No. One revision is not enough. We need the revision history and that
> should no be in the documentation. Your way is also possible, but to what
> revision?
How is the revision history is useful?? Why a simple revision
number is not enough? OK, lets draw a table:
+
On Tue, Aug 07, 2001 at 07:39:49PM +0200, Hojtsy Gabor wrote:
> > > Let's imagine, you start translating mysql.xml. This is not
> > > a small file, so you can't complete it in a day. You copy
> > > the mysql.xml file yourself to a separate directory, as
> > > you probably won't follow the modifica
> > Let's imagine, you start translating mysql.xml. This is not
> > a small file, so you can't complete it in a day. You copy
> > the mysql.xml file yourself to a separate directory, as
> > you probably won't follow the modifications in the mysql.xml
> > file as you translate, because the translat
On Tue, Aug 07, 2001 at 04:55:14PM +0200, Hojtsy Gábor wrote:
> >> So we have a $Revision tag in the english file, showing the actual
> >> english version number. We can have a comment in the translated
> >> version, about what english version number it corresponds to. This
> >> way you can do a d
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
>> So we have a $Revision tag in the english file, showing the actual
>> english version number. We can have a comment in the translated
>> version, about what english version number it corresponds to. This
>> way you
On Tue, Aug 07, 2001 at 01:40:12PM +0200, Hojtsy Gábor wrote:
> >> this is in fact an "automated look into the en-cvs-tree" for
> >more than just
> >> one file.
> >
> >For the other languages it is useless, because we have to look
> >into more
> >revisions besides the last en revision. Most tran
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
>> this is in fact an "automated look into the en-cvs-tree" for
>more than just
>> one file.
>
>For the other languages it is useless, because we have to look
>into more
>revisions besides the last en revi
On Tue, Aug 07, 2001 at 11:39:53AM +0200, Thomas wrote:
> [EMAIL PROTECTED] wrote:
>
> > On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote:
> > > Hojtsy gábor wrote:
> >
> > > > >>I too think that this is not needed for translations. I can't think
> > > > of
> > > > >>any situation where I w
Hi,
I've wrote a simple script to have a snapshot of italian translation
status, module translated, assigned and so on.
This script use some info write on
it/Translators
and some info taked from
en//CVS/Entries
With this scrip you can:
- check which module is assigned ( a option)
Hi Egon,
[EMAIL PROTECTED] wrote:
> On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote:
> > Hojtsy gábor wrote:
>
> > > >>I too think that this is not needed for translations. I can't think
> > > of
> > > >>any situation where I would use this. An En-version comment
> > > >>will be at least
Hello Goba,
Hojtsy gábor wrote:
> >You're right. I use a tag like (proposed by Jeroen I think)
> >
> >As soon as I have enough files with this tag, I'll write a
> >simple script
> >which shows me the priority (which file is farest behind) of
> >"my" files.
> >The more users in our language follo
On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote:
> Hojtsy gábor wrote:
> > >>I too think that this is not needed for translations. I can't think
> > of
> > >>any situation where I would use this. An En-version comment
> > >>will be at least usable :))
> > >Whenever I find out a partally tr
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
>You're right. I use a tag like (proposed by Jeroen I think)
>
>
>As soon as I have enough files with this tag, I'll write a
>simple script
>
>which shows me the priority (which file is farest behind) of
>&q
Hojtsy gábor wrote:
>
>
> >>I too think that this is not needed for translations. I can't think
> of
> >>any situation where I would use this. An En-version comment
> >>will be at least usable :))
> >Whenever I find out a partally translated file, I know at once
> >which version is was started
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
>>I too think that this is not needed for translations. I can't think of
>>any situation where I would use this. An En-version comment
>>will be at least usable :))
>Whenever I find out a partally translated f
on 7/08/01 9:32, Hojtsy Gábor at [EMAIL PROTECTED] wrote:
Hi Goba,
>I too think that this is not needed for translations. I can't think of
>any situation where I would use this. An En-version comment
>will be at least usable :))
Whenever I find out a partally translated file, I know at once
whic
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
>> The reason I added them to 'en', was because translations
>are relative to a
>> en-revision. For translations, that is not true. IMO, it is
>best if there is
>> a En-Revision: 1.XX comment, which is m
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
>> Modified files:
>> /phpdoc/fr bookinfo.xml
>> Log:
>> Adding the revision tag
>
>Is that needed for translations?
>
>The reason I added them to 'en', was because translations are
on 6/08/01 21:50, Jeroen van Wolffelaar at [EMAIL PROTECTED] wrote:
Hi Jeroen,
> Is that needed for translations?
This won't hurt, and this helps me keep track of files, since version is
also written on them.
> The reason I added them to 'en', was because translations are relative to a
> en-rev
> dams Mon Aug 6 06:38:02 2001 EDT
>
> Modified files:
> /phpdoc/fr bookinfo.xml
> Log:
> Adding the revision tag
Is that needed for translations?
The reason I added them to 'en', was because translations are relative to a
en-revision. For translations, that is not true. IMO, it is be
39 matches
Mail list logo
