Re: [Lxde-i18n] LXDE: VCS status

[Martin B. / b. <br...@bs...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2011-06-07 10:56, Pjotr wrote:
> 2011/6/7 Martin Bagge / brother <br...@bs...>:
> On 2011-06-07 10:00, LXDE vcs wrote:
>
>>>> --Status--
>>>> LXSession edit
>>>> #     modified:   po/nl.po
>
> Is there a problem with the Dutch translation that I need to fix now?

Not a problem really. You just forgot to click the commit to vcs link sp
the changes to LXSession Edit is not pushed to the archives and are not
available from our upstream repository.

This is the standard email I send as reminder when I stumble on these.
More or less sent once a week.
- --------------------------------------------
Hi
You seem to have forgotten to push the changes to the VCS. The general
rule of thumb is that you should commit your work at the end of every
session. By that you will not have uncommitted work hanging around
and will not cause merge conflicts that I have to solve. If I run into
conflicts it might mean that I have to reset your file to the state
before you started working on it and all your work will by then be lost.
Remember that I do not speak your languages at all, this makes it almost
impossible to make a good merge.

My proposed workflow is as follows.
1. choose a component to translated
2. do some changes
3. go to the review tab at the po directory
4. click the "commit to vcs"[1] link for the file (languagecode.po)
5. hope for no errors, if not send the error to me in a mail and I'll
try to solve it as good as possible.

extra tip.
When you have visited the review tab you'll find the test cases listed,
click those and skip the false positives but correct any errors that you
might have caused. they are really good!

Thanks alot for your help!

[1] Example screenshot:
http://salyut.bsnet.se/~brother/bilder/ss-101021-vcs_click.png
(just one test case there, endpunc, but you get the idea...)

- --------------------------------------------

The key things in the message is the propsoed workflow and the example
screenshot.

Good luck and thanks for your help!

- -- 
brother
http://sis.bthstudent.se
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJN7gOfAAoJEJbdSEaj0jV7Xq0H/2vmVFKGYcwt3x9OXWbPuEuI
a+BKLh2A5+VXQh+j6TvcmVAOPI3NJRlzh+kKVgYL87Kcctnm5HMeGh1AvsFYqWP7
P8wKYhzi4RiCmjb5fISKGeyVqrG+kOUVXr5gLAb4Igr8Z8nUN8GmobKu67h/jKix
GETqZCNGvH+wTa8i987AJi4r3aE7RkGnQWf9/kqWILLWVTjIbWYZOGYigMCyifCd
dAf3DPHQD90uySl5FSyu0GQeQioM3fyiCy1cigYQ30CAx3JMdYfCtyl1VY3ByiMo
w89IIiyi8Q347mmuucsI7QjhhqNhocoNDRYSIPWSGdJDqj6LrESrrYVeRhkrd7I=
=sdfD
-----END PGP SIGNATURE-----