lists
Frederic Muller
I was wondering if it made sens to separate translation from the discuss
list? Some of us are on both side of the fence, but I find other
translators haven't joined this list and would probably be bored but
most of its content.
Having a translation only list would be for new pot file announcement
and discussion other translation issues.
As I am not 100% sure it's a good idea, I'm asking the group what they
think about the idea?
For the rest, I think discuss is still ok for dev discussion and usage
discussion, but feedback is always welcome.
Thanks.
Fred
ps: it's somehow a way to ask translators to subscribe to something that
matters for them, and for us to give a good communication channel with them.
Andre Roberge
Hi!
I was wondering if it made sens to separate translation from the discuss list? Some of us are on both side of the fence, but I find other translators haven't joined this list and would probably be bored but most of its content.
Having a translation only list would be for new pot file announcement and discussion other translation issues.
As I am not 100% sure it's a good idea, I'm asking the group what they think about the idea?
André
Frederic Muller
On Wed, Jan 20, 2010 at 3:06 AM, Frederic Muller <fr...@beijinglug.org> wrote:
Hi!
I was wondering if it made sens to separate translation from the discuss list? Some of us are on both side of the fence, but I find other translators haven't joined this list and would probably be bored but most of its content.
It should be remembered that, just like in any other open source project, sometimes people will contribute (in this case a translation) just to satisfy a punctual personal need and then move on to something else. I would not necessarily read too much in the fact that some translator have not joined the list.
Having a translation only list would be for new pot file announcement and discussion other translation issues.
As I am not 100% sure it's a good idea, I'm asking the group what they think about the idea?
If someone feels the need for such a list, they should just go ahead. I found that, quite often, issues raised by people doing translations had a positive effect on program development. While there has been a recent flurry of activity on the list, I don't think it is necessarily representative of what it will likely be in a few months, but perhaps (hopefully?) I am mistaken.
I can understand your perspective for having worked on the project since 2004. I also do see rur-ple as a very polished application in almost maintenance mode. At the same time, but getting more into the project I see both little possible improvements and some of the todo I found into the code (I assume put by you) talking about adding turtle in the notebook and such... so maybe there is actually quite some more things to do.
Only time will tell...
But yes, let's see how things evolve and act accordingly.
Thanks.
Fred
Peter Maas
Right, at the same time I wouldn't mind pinging them to get
translations updated ;-)
OK, so pinge me, please :)
Frederic Muller
waiting to be done with the small changes that I'm working on. There is
indeed a new POT file so feel free to update the German version. I would
like to say it's final, but it's the 3rd or 4th time I update it now.
No matter how hard I review anything I always manage to find small
omissions 2 days later...
Making a 100% 'error' free work is really a challenge.
You will notice that I added back lesson previously numbered 43 to 47
after lesson 48 in the English version. Those lessons are not complete
but I was thinking that showing them could entice someone to write them
(Yes, I am an optimist by nature...). I also find lesson 48 last
paragraph making it sound like the classes are over, but this is such a
small detail that we can fix it later.
Thanks.
Fred
Peter Maas
> I still find un-gettextize string every now and then, so I'm kind of
> waiting to be done with the small changes that I'm working on. There is
> indeed a new POT file so feel free to update the German version. I would
> like to say it's final, but it's the 3rd or 4th time I update it now.
Isn't version 1.1 to be released very soon? I assume that all files
will then be tagged as 1.1. I'll take the 1.1. pot file, apply it to
the german translation and tag it also as 1.1. when I'm done. So we
will get a consistent set of program and lessons. I think this is the
only way. Waiting until the english version error free takes probably
too long ;)
> You will notice that I added back lesson previously numbered 43 to 47
> after lesson 48 in the English version. Those lessons are not complete
> but I was thinking that showing them could entice someone to write them
OK, I'll have a look.
> (Yes, I am an optimist by nature...). I also find lesson 48 last
> paragraph making it sound like the classes are over, but this is such a
> small detail that we can fix it later.
Yes, it shoud be open-ended so that we can make a sequel :)
Regards, Peter.
Peter Maas, Aachen, Germany.
Frederic Muller
> Isn't version 1.1 to be released very soon? I assume that all files
> will then be tagged as 1.1. I'll take the 1.1. pot file, apply it to
> the german translation and tag it also as 1.1. when I'm done. So we
> will get a consistent set of program and lessons. I think this is the
> only way. Waiting until the english version error free takes probably
> too long ;)
>
>
was wondering whether it was a 'per file' numbering notation or for the
whole application. As I didn't know, I didn't touch them.
If as you seem to say, it is meant to reflect the application version
number, what do you do with file you do not modify? Do you still change
that version number in the header?
Thanks a lot.
Fred
Peter Maas
> Yes I'm glad you brought this point. I noticed the file versioning and
> was wondering whether it was a 'per file' numbering notation or for the
> whole application. As I didn't know, I didn't touch them.
>
> If as you seem to say, it is meant to reflect the application version
> number, what do you do with file you do not modify? Do you still change
> that version number in the header?
Every commit (i.e. a set of additions, deletions and modifications)
increases the repository's revision by 1. The files which were
committed for this revision are the "affected files" of the revision.
Go to http://code.google.com/p/rur-ple. Click the source tab. Click on
changes. You'll see the list of revisions. Click on revision 96 (r96)
to see the list of affected files of r96. Which files will be copied
to your disk if you check out r96? Only the affected files? No, all
files which were added (and not deleted) until (including) r96. The
files which were not affected by r96 will be copied as most recent
before r96. Take rur_start.py as an example. It was added in rev. 3
and modified in r18. If you check out the repository r17 your working
directory will contain rur_start.py of r3. If you check out the
repository r19 your working directory will contain rur_start.py of
r18. Revisions are managed automatically by SVN. But they are not
sufficient because not every repository revision has release quality.
If you have created a repository revisions that works and has all
features you want to see in version 1.1 then you tag this revision as
1.1. This means that all files which are to be part of version 1.1 are
tagged (marked) with 1.1. So you establish the 1.1 version in the
repository.