GNOME Bugzilla – Bug 680546
Dead link on documentation
Last modified: 2012-07-27 12:59:33 UTC
Hi all, There's a dead link in the documentation. String ID is 1162: The way it works is that you contact the gnome-i18n mailing list to find out how the translators can access your <filename>po/</filename> subdirectory, and to add your project to the big <ulink url="http://developer.gnome.org/projects/gtp/status/">status tables</ulink>. http://developer.gnome.org/projects/gtp/status/ does not exist anymore. Maybe the link should be updated to http://l10n.gnome.org/module/ Thanks in advance!
String IDs are totally based on the application that you use for translating and don't mean much globally. Could you provide the filename and line number instead?
I found the string "The way it works is that you contact......" in file http://git.gnome.org/browse/gtkmm-documentation/tree/docs/tutorial/C/gtkmm-tutorial-in.xml lines 6962-6967. You can test the dead link at http://developer.gnome.org/gtkmm-tutorial/stable/sec-i18n-getting-help-with-translations.html.en
OK, next time I'll try to check where the string comes from browsing the git repository.
These are broken links in gtkmm-tutorial-in.xml: http://svn.gnome.org/viewcvs/intltool/trunk/README?view=markup http://developer.gnome.org/doc/tutorials/gnome-i18n/translator.html http://www.cs.auc.dk/~olau/compose/ http://developer.gnome.org/projects/gtp/ http://developer.gnome.org/projects/gtp/status/ Replacements: http://svn.gnome.org/viewcvs/intltool/trunk/README?view=markup http://freedesktop.org/wiki/Software/intltool/ ??? http://developer.gnome.org/doc/tutorials/gnome-i18n/translator.html https://live.gnome.org/TranslationProject/ ??? http://www.cs.auc.dk/~olau/compose/ http://developer.gnome.org/glibmm/unstable/classGlib_1_1ustring.html (&url_refdocs_base_glib;ustring.html) I don't understand why the gtkmm tutorial recommends C-style sprintf() or an external compose library, when Glib::ustring::compose() does what the compose library is said to do. http://developer.gnome.org/projects/gtp/ to http://l10n.gnome.org http://developer.gnome.org/projects/gtp/status/ to http://l10n.gnome.org/module/ Even though http://svn.gnome.org/viewcvs/gnome-common/trunk/autogen.sh?view=markup is not broken, I suspect that it should be replaced by http://git.gnome.org/browse/gnome-common/tree/autogen.sh I'll make another attempt to find good replacements for the first two broken links. Or does anyone else know? Nicolás, since you're a translator, perhaps you know if only the links shall be changed in the "Getting help with translations" section. Does the text also need changes?
I think the text is fine as long as the links are changed so that they point to the current translation project. However, I don't like the idea of having to ask gnome-i18n for instructions regarding how translators can access the po subdirectory. -- Quoting: The way it works is that you contact the gnome-i18n mailing list to find out how the translators can access your po/ subdirectory -- Maybe that information could be added directly into the documentation (or the GNOME wiki) so that the i18n team don't have to answer the same question a lot of times.
Better replacements of links: http://svn.gnome.org/viewcvs/intltool/trunk/README?view=markup http://bazaar.launchpad.net/~intltool/intltool/trunk/view/head:/README http://developer.gnome.org/doc/tutorials/gnome-i18n/translator.html https://live.gnome.org/TranslationProject/GitHowTo Change the linked text to "How to use Git for GNOME translators". http://www.cs.auc.dk/~olau/compose/ http://developer.gnome.org/glibmm/unstable/classGlib_1_1ustring.html (&url_refdocs_base_glib;ustring.html) Same as in comment 4. http://developer.gnome.org/projects/gtp/ https://live.gnome.org/TranslationProject/ http://developer.gnome.org/projects/gtp/status/ http://l10n.gnome.org/module/ Same as in comment 4. (In reply to comment #5) > Maybe that information could be added directly into the documentation (or the > GNOME wiki) so that the i18n team don't have to answer the same question a > lot of times. There's a lot of information at https://live.gnome.org/TranslationProject/ and the web pages linked to from there, perhaps too much information. I can't find a description of what an application programmer shall do to make translators aware that there is a new module that could benefit from being translated. Do you know what he/she should do? Or where the information can be found? I think it should be described in the Wiki of the GNOME Translation Project rather than in the gtkmm tutorial. Many application programs are written in other programming languages than C++; often C, sometimes Python. I suppose the actions to take by the application programmer are independent of the programming language.
(In reply to comment #6) > Do you know what he/she should do? Or where the information can be > found? I found some information digging the i18n mailing list archive. It seems that uploading your application sources (with the .po folder and its files) to the git repo is enough to get the stats automagically on Damned Lies. It's still a good idea to contact the i18n list so that translators get notified that there's a new module to be translated. You can also check here: https://live.gnome.org/GitMigration/Translators that "Damned Lies is already able to track git (along cvs, svn, bzr and hg) modules and to generate stats for them."
(In reply to comment #7) > I found some information digging the i18n mailing list archive. Where? Link(s) to interesting post(s)? > It seems that uploading your application sources (with the .po folder and > its files) to the git repo is enough to get the stats automagically > on Damned Lies. Are you sure the addition to Damned Lies' module list is automagic? There are several modules in git.gnome.org, which are not in the module list http://l10n.gnome.org/module/. E.g. gtkmm, glibmm, libsigc++2. Those modules don't contain any translatable strings. Would they automatically pop up in the DL module list if a po/ directory and appropriate files were added? A think I'll just fix the broken links and keep the text in the "Getting help with translations" section, unless I get a text that I can copy with little or no modification. Although I agree with you that the suggestion to ask for information on the gnome-i18n list is not ideal.
(In reply to comment #8) > (In reply to comment #7) > > I found some information digging the i18n mailing list archive. > > Where? Link(s) to interesting post(s)? Oh, it seems I read an old post: https://mail.gnome.org/archives/gnome-i18n/2005-September/msg00349.html A newer post suggests developers "have" to ask once they uploaded the sources to git: https://mail.gnome.org/archives/gnome-i18n/2010-December/msg00012.html And this one, even newer, also does. https://mail.gnome.org/archives/gnome-i18n/2011-March/msg00353.html > A think I'll just fix the broken links and keep the text in the "Getting help > with translations" section Maybe you should just add some text telling the developer to first upload the sources to git and then ask for help with translations.
Pushed this commit: http://git.gnome.org/browse/gtkmm-documentation/commit/?id=0d2e93a0f277c5484a6a489f94b68761c8023f6d