About translating MuseScore
|
|
Thomas Bonte
|
Part of the success of MuseScore is thanks to the availability of many translations. Twenty so far and counting, added in the past 2 years, from Chinese up to Galician. All thanks to the 30+ MuseScore translators.
While adding a new translation is just a matter of adding a few extra lines of code, the main challenge is to keep the translations up to date. Each MuseScore release is shipped together with all its translations which makes the challenge even harder. We did a call during the 0.9.5 code freeze, to get much translated as possible but that's kinda tough when translating can only be done by one translator at the time. Also the hassle with uploading the ts (translation) files to the forum, committing them to the code repository and finally opening them up for other translators, takes a quite some time and effort. With a new language added each month on average, it's time to improve the translation workflow. The ideal solution would be: 1. Have a centralized translation server running on translate.musescore.org where all the languages can easily be translated in a collaborative way. 2. Package the translations per release and make them available for download on musescore.org. Ideally, MuseScore could download the language pack directly from musescore.org and install it for the user. To create this solution, we will be using Drupal and the excellent localization server module. Custom coding will be required because this l10n server handles po files only, while MuseScore uses ts files. So a custom import & export filter will have to be written. It's also not clear yet how the syncing with the SVN repository will work out: will it only be possible to translate releases, or can the HEAD also be imported on regular basis and committed back to the SVN. All questions for the coming months. If you want to contribute to this task, don't hesitate to leave a comment or mail directly. |
|
Thomas Bonte
|
A sneak preview of the translating server: http://translate.musescore.org
You can log in with your musescore.org credentials and see how the translation workflow looks like and even give it a try. Keep in mind that we are still testing so all your changes can and most likely will be erased up until we are sure it works the way we want. So don't start translating for real yet. The main issue being worked on currently is to make sure the code repository can sync with the translation server.
|
||||||||||||||||
Per Holje
|
This is absolutely an improvement to the workflow, and I hope it can be made
to work smoothly enough. I have some initial thoughts: - We need the ability to download interim builds of the translations, to be able to test the translations. - It would be nice to be able to sort the list of strings, to make it easier to spot inconsistencies in the translated terms. - I'm not sure how the "Translate" button (at the right of each item) is supposed to work. It does not seem to do anything... - There should be some context information about each item, where the string is used, so we can find it in the MuseScore GUI. Keep up the good work! :per Fredag 16. oktober 2009 13.59.35 skrev Thomas Bonte : > A sneak preview of the translating server: http://translate.musescore.org > > You can log in with your musescore.org credentials and see how the > translation workflow looks like and even give it a try. Keep in mind that > we are still testing so all your changes can and most likely will be > erased up until we are sure it works the way we want. So don't start > translating for real yet. > > The main issue being worked on currently is to make sure the code > repository can sync with the translation server. > > Thomas Bonte wrote: > > Part of the success of MuseScore is thanks to the availability of many > > translations. Twenty so far and counting, added in the past 2 years, from > > Chinese up to Galician. All thanks to the 30+ MuseScore translators. > > > > While adding a new translation is just a matter of adding a few extra > > lines of code, the main challenge is to keep the translations up to date. > > Each MuseScore release is shipped together with all its translations > > which makes the challenge even harder. > > http://www.musescore.org/en/node/2271 We did a call during the 0.9.5 > > code freeze, to get much translated as possible but that's kinda tough > > when translating can only be done by one translator at the time. Also the > > hassle with uploading the ts > > (translation) files to the forum, committing them to the code repository > > and finally opening them up for other translators, takes a quite some > > time and effort. With a new language added each month on average, it's > > time to improve the translation workflow. > > > > The ideal solution would be: > > 1. Have a centralized translation server running on > > translate.musescore.org where all the languages can easily be translated > > in a collaborative way. > > 2. Package the translations per release and make them available for > > download on musescore.org. Ideally, MuseScore could download the language > > pack directly from musescore.org and install it for the user. > > > > To create this solution, we will be using http://www.drupal.org Drupal > > and the excellent http://drupal.org/project/l10n_server localization > > server module. Custom coding will be required because this l10n server > > handles po files only, while MuseScore uses ts files. So a custom import > > & export filter will have to be written. It's also not clear yet how the > > syncing with the SVN repository will work out: will it only be possible > > to translate releases, or can the HEAD also be imported on regular basis > > and committed back to the SVN. All questions for the coming months. If > > you want to contribute to this task, don't hesitate to leave a comment or > > http://www.musescore.org/contact mail directly . > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
||||||||||||||||
David Bolton-2
|
In reply to this post
by Thomas Bonte
Thomas,
It looks like it should be much easier for new comers to get started translating MuseScore. I also like how it clearly shows the overall status for each language. I'm not one of the translators but if I was this would be my one feature request: in the "Limit" drop-down menu could you add options for 50 and 100 items per page? I prefer to have a lots off information on one page. Maybe others are like me. David Thomas Bonte wrote: > A sneak preview of the translating server: http://translate.musescore.org > > You can log in with your musescore.org credentials and see how the > translation workflow looks like and even give it a try. Keep in mind that we > are still testing so all your changes can and most likely will be erased up > until we are sure it works the way we want. So don't start translating for > real yet. > > The main issue being worked on currently is to make sure the code repository > can sync with the translation server. > > > Thomas Bonte wrote: > >> Part of the success of MuseScore is thanks to the availability of many >> translations. Twenty so far and counting, added in the past 2 years, from >> Chinese up to Galician. All thanks to the 30+ MuseScore translators. >> >> While adding a new translation is just a matter of adding a few extra >> lines of code, the main challenge is to keep the translations up to date. >> Each MuseScore release is shipped together with all its translations which >> makes the challenge even harder. http://www.musescore.org/en/node/2271 We >> did a call during the 0.9.5 code freeze, to get much translated as >> possible but that's kinda tough when translating can only be done by one >> translator at the time. Also the hassle with uploading the ts >> (translation) files to the forum, committing them to the code repository >> and finally opening them up for other translators, takes a quite some time >> and effort. With a new language added each month on average, it's time to >> improve the translation workflow. >> >> The ideal solution would be: >> 1. Have a centralized translation server running on >> translate.musescore.org where all the languages can easily be translated >> in a collaborative way. >> 2. Package the translations per release and make them available for >> download on musescore.org. Ideally, MuseScore could download the language >> pack directly from musescore.org and install it for the user. >> >> To create this solution, we will be using http://www.drupal.org Drupal >> and the excellent http://drupal.org/project/l10n_server localization >> server module. Custom coding will be required because this l10n server >> handles po files only, while MuseScore uses ts files. So a custom import & >> export filter will have to be written. It's also not clear yet how the >> syncing with the SVN repository will work out: will it only be possible to >> translate releases, or can the HEAD also be imported on regular basis and >> committed back to the SVN. All questions for the coming months. If you >> want to contribute to this task, don't hesitate to leave a comment or >> http://www.musescore.org/contact mail directly . >> ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
||||||||||||||||
|
Thomas Bonte
|
Hi Per, David,
Thanks for the helpful reactions. Currently, there is a major UI improvement in the pipeline but it is not deployed yet on translate.musescore.org. You can see it here in a screencast: http://vimeo.com/6944071 I'm sure this will make it much easier to understand how the translation workflow works. I'll post when this UI improvement is deployed. It might take some time however, but eventually I don't see any barriers anymore for step 1 although it will require some more custom coding.
|
||||||||||||||||
|
Thomas Bonte
|
In reply to this post
by Per Holje
Hi Per,
The translation server has now been improved with two of your proposed ideas. Head over to http://translate.musescore.org/en/translate/languages/da -> Via the download tab, you will be able to get the latest ts and qm file. These files will be created on regular basis but it can be manually triggered as well (if you have the permissions). -> When you browse through the source strings, you will see the context below it. You can also filter on context. Other than that, the translate workflow will improve in the future, but for the moment, if there aren't any other crucial features missing, I think the translation server can be launched officially somewhere in November.
|
||||||||||||||||
|
Per Holje
|
Very nice!
I was not able to download the .ts or .qm files, is this supposed to work yet? :per Søndag 1. november 2009 21.38.27 skrev Thomas Bonte : > Hi Per, > > The translation server has now been improved with two of your proposed > ideas. Head over to > http://translate.musescore.org/en/translate/languages/da > > -> Via the download tab, you will be able to get the latest ts and qm file. > These files will be created on regular basis but it can be manually > triggered as well (if you have the permissions). > > -> When you browse through the source strings, you will see the context > below it. You can also filter on context. > > Other than that, the translate workflow will improve in the future, but for > the moment, if there aren't any other crucial features missing, I think the > translation server can be launched officially somewhere in November. > > Per Holje wrote: > > This is absolutely an improvement to the workflow, and I hope it can be > > made > > to work smoothly enough. I have some initial thoughts: > > > > - We need the ability to download interim builds of the translations, to > > be > > able to test the translations. > > - It would be nice to be able to sort the list of strings, to make it > > easier > > to spot inconsistencies in the translated terms. > > - I'm not sure how the "Translate" button (at the right of each item) is > > supposed to work. It does not seem to do anything... > > - There should be some context information about each item, where the > > string > > is used, so we can find it in the MuseScore GUI. > > > > Keep up the good work! > > > > :per > > > > Fredag 16. oktober 2009 13.59.35 skrev Thomas Bonte : > >> A sneak preview of the translating server: > >> http://translate.musescore.org > >> > >> You can log in with your musescore.org credentials and see how the > >> translation workflow looks like and even give it a try. Keep in mind > >> that we are still testing so all your changes can and most likely will > >> be erased up until we are sure it works the way we want. So don't start > >> translating for real yet. > >> > >> The main issue being worked on currently is to make sure the code > >> repository can sync with the translation server. > >> > >> Thomas Bonte wrote: > >> > Part of the success of MuseScore is thanks to the availability of many > >> > translations. Twenty so far and counting, added in the past 2 years, > >> > >> from > >> > >> > Chinese up to Galician. All thanks to the 30+ MuseScore translators. > >> > > >> > While adding a new translation is just a matter of adding a few extra > >> > lines of code, the main challenge is to keep the translations up to > >> > >> date. > >> > >> > Each MuseScore release is shipped together with all its translations > >> > which makes the challenge even harder. > >> > http://www.musescore.org/en/node/2271 We did a call during the 0.9.5 > >> > code freeze, to get much translated as possible but that's kinda tough > >> > when translating can only be done by one translator at the time. Also > >> > >> the > >> > >> > hassle with uploading the ts > >> > (translation) files to the forum, committing them to the code > >> > >> repository > >> > >> > and finally opening them up for other translators, takes a quite some > >> > time and effort. With a new language added each month on average, it's > >> > time to improve the translation workflow. > >> > > >> > The ideal solution would be: > >> > 1. Have a centralized translation server running on > >> > translate.musescore.org where all the languages can easily be > >> > >> translated > >> > >> > in a collaborative way. > >> > 2. Package the translations per release and make them available for > >> > download on musescore.org. Ideally, MuseScore could download the > >> > >> language > >> > >> > pack directly from musescore.org and install it for the user. > >> > > >> > To create this solution, we will be using http://www.drupal.org > >> > Drupal and the excellent http://drupal.org/project/l10n_server > >> > localization server module. Custom coding will be required because > >> > this l10n server handles po files only, while MuseScore uses ts files. > >> > So a custom > >> > >> import > >> > >> > & export filter will have to be written. It's also not clear yet how > >> > >> the > >> > >> > syncing with the SVN repository will work out: will it only be > >> > possible to translate releases, or can the HEAD also be imported on > >> > regular > >> > >> basis > >> > >> > and committed back to the SVN. All questions for the coming months. If > >> > you want to contribute to this task, don't hesitate to leave a comment > >> > >> or > >> > >> > http://www.musescore.org/contact mail directly . > > > > ------------------------------------------------------------------------- > >----- Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > Mscore-developer mailing list > > [hidden email] > > https://lists.sourceforge.net/lists/listinfo/mscore-developer > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
