Re: Priority 1 Translation of web site to spanish
Francisco Vila wrote: > El vie, 29 de dic de 2006, a las 12:54:58 -0600, Daniel Tonda Castillo dijo: > > > >Another nitpick: are you the only translator or are you in a team? All > > >translators should be credited in about/thanks#website. > > > > > There's Francisco Vila also. > > ...but he's not yet working on it. I do not deserve to be the first in the > list of spanish translators, I think. IMHO the important point to know about is whether you have enough contributed to the translation to be mentioned on this page. If you have already contributed in some way, and if you really prefer, it could read "Daniel Tonda Castillo, Spanish translation, with help from Fransisco Vila." Happy new year and good luck for the translation, -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
El vie, 29 de dic de 2006, a las 12:54:58 -0600, Daniel Tonda Castillo dijo: > >Another nitpick: are you the only translator or are you in a team? All > >translators should be credited in about/thanks#website. > > > There's Francisco Vila also. ...but he's not yet working on it. I do not deserve to be the first in the list of spanish translators, I think. -- Francisco Vila Doncel. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Just as in the lilypond documentation: Git: ... in small digestible and programmable chunks... Thanks, I've been re-reading this thread, I'll get it bit by bit but I will. ;) Daniel T. 2006/12/30, Johannes Schindelin <[EMAIL PROTECTED]>: Hi, On Fri, 29 Dec 2006, Daniel Tonda Castillo wrote: > From what I gather, so far if no write acces is provided, the most > important git commands would seem to be clone and patch, but patch is > still not clear for me yet. The most important git command (at least to me) is git-diff. Say, your local branch is named "myweb" and is derived from "web/master" (you can start such a branch by "git checkout -b myweb web/master"). Now you want to see all changes between the original web/master and your myweb: $ git diff web/master..myweb Note that it automatically pages the output. But these are many changes, and now you are only interested in your changes to the file README: $ git diff web/master..myweb README And then, you did a few changes and want to verify that all you did since the last commit looks sane: $ git diff This gives you the changes which will be committed by a "git commit -a". Maybe you found a little typo in the file AUTHORS. Fix it and verify with $ git diff AUTHORS that all is fine. So, why did I mention format-patch in another mail instead of diff? Because you are most likely committing in small, logically separated steps, and you do not want to submit one big unauditable diff, but rather several easy-to-verify patches. So, format-patch creates nice files from the commits you created. BTW git has also something like "patch": it is called git-apply (I don't really know why Linus did not call it "patch"). Something like $ git apply < a-diff-from-somebody-else will do almost the same as patch, but it recognizes the renaming and copying enhancements from git's diff format. Another quite useful command is git-show. Given a committish, you can look at the diff and the commit message (it is automatically paged): $ git show web/master~2 shows the parent of the parent of the current tip of web/master. In the upcoming git release, 1.5.0 (due mid February), git show can also show directories and files: $ git show han-wen:README shows you what the file README looks like in the branch han-wen. That's it for today's git lesson, brought to you by a very happy LilyPond user. Ciao, Dscho -- Daniel Tonda C. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Hi, On Fri, 29 Dec 2006, Daniel Tonda Castillo wrote: > From what I gather, so far if no write acces is provided, the most > important git commands would seem to be clone and patch, but patch is > still not clear for me yet. The most important git command (at least to me) is git-diff. Say, your local branch is named "myweb" and is derived from "web/master" (you can start such a branch by "git checkout -b myweb web/master"). Now you want to see all changes between the original web/master and your myweb: $ git diff web/master..myweb Note that it automatically pages the output. But these are many changes, and now you are only interested in your changes to the file README: $ git diff web/master..myweb README And then, you did a few changes and want to verify that all you did since the last commit looks sane: $ git diff This gives you the changes which will be committed by a "git commit -a". Maybe you found a little typo in the file AUTHORS. Fix it and verify with $ git diff AUTHORS that all is fine. So, why did I mention format-patch in another mail instead of diff? Because you are most likely committing in small, logically separated steps, and you do not want to submit one big unauditable diff, but rather several easy-to-verify patches. So, format-patch creates nice files from the commits you created. BTW git has also something like "patch": it is called git-apply (I don't really know why Linus did not call it "patch"). Something like $ git apply < a-diff-from-somebody-else will do almost the same as patch, but it recognizes the renaming and copying enhancements from git's diff format. Another quite useful command is git-show. Given a committish, you can look at the diff and the commit message (it is automatically paged): $ git show web/master~2 shows the parent of the parent of the current tip of web/master. In the upcoming git release, 1.5.0 (due mid February), git show can also show directories and files: $ git show han-wen:README shows you what the file README looks like in the branch han-wen. That's it for today's git lesson, brought to you by a very happy LilyPond user. Ciao, Dscho ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Daniel Tonda Castillo wrote: > John Mandereau wrote: > > Daniel Tonda Castillo wrote: > >> From what I gather, so far if no write acces is provided, the most > >> important git commands would seem to be clone and patch, but patch is > >> still not clear for me yet. > >> > > > > No, you only use clone to initially clone the repository, then you do > > git-pull to update (see Johannes Schindelin's message sent today at > > 18:01 for a good explanation, or wait for me to update the README file). > > > Ok, now in the original README: > After translating I do: > git-add > git commit -m 'add file' It is better to commit all files in a whole: run 'git-update-index' on each file, then 'git-commit -m "message"' without giving any file. > scripts/check-translation.py You should do that before the commit, in order to avoid committing again in case you would have to correct the committish. Note you can also run 'make LANG=es check-translation' to check all files in one go. -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
John Mandereau wrote:
Daniel Tonda Castillo wrote:
John Mandereau wrote:
[...]
From what I gather, so far if no write acces is provided, the most
important git commands would seem to be clone and patch, but patch is
still not clear for me yet.
No, you only use clone to initially clone the repository, then you do
git-pull to update (see Johannes Schindelin's message sent today at
18:01 for a good explanation, or wait for me to update the README file).
Ok, now in the original README:
After translating I do:
git-add
git commit -m 'add file'
scripts/check-translation.py
Yes, that looks good. The committish number is in fact the checksum of
the last commit, so it is not associated to any particular file. After
you made sure the translation is up to date (ie you checked against the
English pages or you updated translations according to 'make LANG=es
chack-translation' output), the most simple thing to do is to copy the
last committish into the concerned translated files. Btw, isn't
scripts/rev-to-commit.py intended to automate this work?
So all the website if there are no commits would have the same committish?
Yes. My last question was asked to the developers.
When and if you upload, the next time I would do git-clone again and It
will overwrite whatever I did with what is on the server?
No. First, it is git-pull; in fact you should first commit your changes
to your local copy of the repository, so there isn't any conflict when
you update from the sv.gnu.org repository. To be precise, you should do
the following commands at top of the source directory:
git-add po/es.po
... and do the same for every new file (do 'git-status' to see which
files are untracked, deleted, or changed and not committed).
Then do
git-pull origin
It should fetch the remote repository (ie update the local copy of the
remote branch, called 'origin'), then merge the 'origin' branch into
'master' ('master' is the local branch you work on).
You can list the branches with 'git-show-branch'.
ok
Thanks. The translation is online; can you check whether the pages are
OK (ideally you should see translated pages automagically when visiting
lilypond.org with your browser),
¡Looks great!
and can you please write a short
announcement in Spanish, which will be added to the news section?
Announcement:
-
¡Ya está disponible la versión en español del sitio web de LilyPond!
-
Thanks in advance,
Daniel Tonda C.
begin:vcard
fn:Daniel Tonda Castillo
n:Tonda Castillo;Daniel
email;internet:[EMAIL PROTECTED]
version:2.1
end:vcard
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Daniel Tonda Castillo wrote:
> John Mandereau wrote:
[...]
> From what I gather, so far if no write acces is provided, the most
> important git commands would seem to be clone and patch, but patch is
> still not clear for me yet.
No, you only use clone to initially clone the repository, then you do
git-pull to update (see Johannes Schindelin's message sent today at
18:01 for a good explanation, or wait for me to update the README file).
> > Yes, that looks good. The committish number is in fact the checksum of
> > the last commit, so it is not associated to any particular file. After
> > you made sure the translation is up to date (ie you checked against the
> > English pages or you updated translations according to 'make LANG=es
> > chack-translation' output), the most simple thing to do is to copy the
> > last committish into the concerned translated files. Btw, isn't
> > scripts/rev-to-commit.py intended to automate this work?
> >
> So all the website if there are no commits would have the same committish?
Yes. My last question was asked to the developers.
> When and if you upload, the next time I would do git-clone again and It
> will overwrite whatever I did with what is on the server?
No. First, it is git-pull; in fact you should first commit your changes
to your local copy of the repository, so there isn't any conflict when
you update from the sv.gnu.org repository. To be precise, you should do
the following commands at top of the source directory:
git-add po/es.po
... and do the same for every new file (do 'git-status' to see which
files are untracked, deleted, or changed and not committed).
Then do
git-pull origin
It should fetch the remote repository (ie update the local copy of the
remote branch, called 'origin'), then merge the 'origin' branch into
'master' ('master' is the local branch you work on).
You can list the branches with 'git-show-branch'.
> > What's the Spanish for 'Spanish'? It could be used in the 'Other
> > languages' menu preferably to the English 'Spanish' ;-)
> >
> Ok, the spanish for spanish is: "Español".
Thanks. The translation is online; can you check whether the pages are
OK (ideally you should see translated pages automagically when visiting
lilypond.org with your browser), and can you please write a short
announcement in Spanish, which will be added to the news section?
Thanks in advance,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Han-Wen Nienhuys wrote: Daniel Tonda Castillo escreveu: The instructions on the wiki are only intended to give useful hints and to avoid reading full git documentation. That's not been achieved yet, as there are more useful git/cg commands than with cvs. Anyway, the Translations HOWTO is a complement to README and TRANSLATION, which are the official instructions. From what I gather, so far if no write acces is provided, the most important git commands would seem to be clone and patch, but patch is still not clear for me yet. I don't mind providing write access, but I think it's best if you get a little comfortable with using GIT first. You are indeed a wise man, ¡I'd probably wreak havoc! I've also taken the liberty of adding Franciso and myself to the thanks.html page for the spanish translation in the phase 2 documents, which I'll mail shortly. Daniel Tonda C. begin:vcard fn:Daniel Tonda Castillo n:Tonda Castillo;Daniel email;internet:[EMAIL PROTECTED] version:2.1 end:vcard ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
John Mandereau <[EMAIL PROTECTED]> writes: >> I'm attaching a bzipped tarball containing the priority 1 items in the >> TRANSLATION document, following the instructions on the wiki. > > Great, I've committed and pushed to web/master. Han-Wen and/or Jan may > still add some stuff so that the translation really comes online. Thanks, that's great. It's online! Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Daniel Tonda Castillo escreveu: >> The instructions on the wiki are only intended to give useful hints and >> to avoid reading full git documentation. That's not been achieved yet, >> as there are more useful git/cg commands than with cvs. Anyway, the >> Translations HOWTO is a complement to README and TRANSLATION, which are >> the official instructions. >> >> > From what I gather, so far if no write acces is provided, the most > important git commands would seem to be clone and patch, but patch is > still not clear for me yet. I don't mind providing write access, but I think it's best if you get a little comfortable with using GIT first. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
John Mandereau wrote: Le vendredi 29 décembre 2006 à 04:51 -0600, Daniel Tonda a écrit : Hello: I'm attaching a bzipped tarball containing the priority 1 items in the TRANSLATION document, following the instructions on the wiki. Great, I've committed and pushed to web/master. Han-Wen and/or Jan may still add some stuff so that the translation really comes online. The instructions on the wiki are only intended to give useful hints and to avoid reading full git documentation. That's not been achieved yet, as there are more useful git/cg commands than with cvs. Anyway, the Translations HOWTO is a complement to README and TRANSLATION, which are the official instructions. From what I gather, so far if no write acces is provided, the most important git commands would seem to be clone and patch, but patch is still not clear for me yet. Thanks to Manuel, who pointed out some mistakes in the beginner's tutorial i went over the web site again and revised some stuff. What do you mean? What have you exactly revised? Ortographic errors in the spanish version which I thought was finished but was not. Yes, that looks good. The committish number is in fact the checksum of the last commit, so it is not associated to any particular file. After you made sure the translation is up to date (ie you checked against the English pages or you updated translations according to 'make LANG=es chack-translation' output), the most simple thing to do is to copy the last committish into the concerned translated files. Btw, isn't scripts/rev-to-commit.py intended to automate this work? So all the website if there are no commits would have the same committish? When and if you upload, the next time I would do git-clone again and It will overwrite whatever I did with what is on the server? What's the Spanish for 'Spanish'? It could be used in the 'Other languages' menu preferably to the English 'Spanish' ;-) Ok, the spanish for spanish is: "Español". Another nitpick: are you the only translator or are you in a team? All translators should be credited in about/thanks#website. There's Francisco Vila also. begin:vcard fn:Daniel Tonda Castillo n:Tonda Castillo;Daniel email;internet:[EMAIL PROTECTED] version:2.1 end:vcard ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Le vendredi 29 décembre 2006 à 18:28 +0100, John Mandereau a écrit : > Le vendredi 29 décembre 2006 à 04:51 -0600, Daniel Tonda a écrit : > > Hello: > > > > I'm attaching a bzipped tarball containing the priority 1 items in the > > TRANSLATION document, following the instructions on the wiki. > > Great, I've committed and pushed to web/master. Han-Wen and/or Jan may > still add some stuff so that the translation really comes online. I've added the necessary bits for this and checked 'make' output, and I finally thought it was good to commit and push, so all should be online in a couple of hours. Don't forget questions in my previous email. Cheers, -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Priority 1 Translation of web site to spanish
Le vendredi 29 décembre 2006 à 04:51 -0600, Daniel Tonda a écrit : > Hello: > > I'm attaching a bzipped tarball containing the priority 1 items in the > TRANSLATION document, following the instructions on the wiki. Great, I've committed and pushed to web/master. Han-Wen and/or Jan may still add some stuff so that the translation really comes online. The instructions on the wiki are only intended to give useful hints and to avoid reading full git documentation. That's not been achieved yet, as there are more useful git/cg commands than with cvs. Anyway, the Translations HOWTO is a complement to README and TRANSLATION, which are the official instructions. > Thanks to Manuel, who pointed out some mistakes in the beginner's > tutorial i went over the web site again and revised some stuff. What do you mean? What have you exactly revised? > As far as I understand the wiki, all the pages have the same > committish number: ac5da2c7e90f10ce8a680b275d1e33b10462c4ea, so that > is what goes at the top of each file. Yes, that looks good. The committish number is in fact the checksum of the last commit, so it is not associated to any particular file. After you made sure the translation is up to date (ie you checked against the English pages or you updated translations according to 'make LANG=es chack-translation' output), the most simple thing to do is to copy the last committish into the concerned translated files. Btw, isn't scripts/rev-to-commit.py intended to automate this work? What's the Spanish for 'Spanish'? It could be used in the 'Other languages' menu preferably to the English 'Spanish' ;-) Another nitpick: are you the only translator or are you in a team? All translators should be credited in about/thanks#website. -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
