Re: Translations for Glabels 4.0
Hello all, Am Do., 1. Nov. 2018 um 10:04 Uhr schrieb Mario Blättermann : > > Dear translators, > > the po files for Glabels are maintained in the Damned Lies pages for more than > ten years. Thanks for all your work on making Glabels better by translating it > into many languages! > > But Glabels development has been switched from GTK to Qt, and the version > control system now resides at Github [1]. The upcoming major version 4.0 will > be based on Qt. Along with the Qt port, we are no longer using po files, but > ts files. We have a new project at the Zanata translation management > platform [2]. If you are willing to continue translating Glabels, please > create an account there. > > As far as it was possible, we have migrated existing translations from Damned > Lies, the translation status is mostly around 30%. So almost all languages > are still available, with one exception: The Zanata platform doesn't support > ca@valencia, so this po file hasn't been imported. Note, we have split the > translations into two files, the templates are now handled separate from the > GUI. > > For the time being, we host only the GUI translations there. Once we have a > user manual again, this will become also available for translation (probably > also the man pages). > > [1] https://github.com/jimevins/glabels-qt > [2] https://translate.zanata.org/project/view/Glabels > After detecting some serious problems with Zanata, we have decided to move the translations of glabels-qt to another platform. During the last months, it happened twice that the web interface went down and came up again some days later (see [1]). This is very annoying for both translators and maintainers. Moreover, Zanata is unable to handle *.ts files properly. Such files will be converted internally to *.po files, and we get then translated *.po files back. Well, it is possible to convert them back to *.ts, but the file hierarchy needs also to be adjusted, which is more work than it's worth. So we have moved the translations to Transifex [2]. If someone of you is still willing to continue on translating Glabels, subscribe to Transifex please. The *.ts files imported from the old *.po files are available from the Github repo of Glabels-qt [3]. Due to the conversion all of the strings have been marked as »unfinished«, and such files only with fuzzy strings are not accepted by Transifex. [1] https://www.redhat.com/archives/zanata-users/2019-April/msg5.html [2] https://www.transifex.com/glabels/glabels-ui/dashboard/ [3] https://github.com/jimevins/glabels-qt/tree/master/translations Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Unauthorized translation changes in dconf-editor
Hello Arnaud, Arnaud Bonatti via gnome-i18n schrieb am Di., 19. März 2019, 16:43: > Hi Alexandre, > > 2019-03-19 11:06 UTC+01:00, Alexandre Franke : > > Sadly whether we translate it or not, it will still be seen as “GNOME > > software” (it lives in GNOME/ on gitlab) and his behaviour will hurt > > the good reputation of our translation work. If he’s not up to the > > task of maintaining that piece of software correctly then he should be > > handled in an appropriate way. > > Honestly, I though at the opposite that this way to do things would > please both translators and users. > > Users, because it brings to them fixes to translations in a fast way > (with some errors –I’m human, and do not write all languages on Earth– > but mostly with improvements), and with less regressions also, as my > patches are “saving” some old strings from not being applied. > > Translators, because I was giving back to them my suggestions, so that > they could apply it or dismiss it in the main po/ files, a good way to > improve their translations faster than before, and a real quality > assurance, as I’m reading translations with a completely different > vision of the application and with a complete knowledge on what each > string does and where it goes (in the same logic, I also tried by the > way to help translators here by adding comments in the code). > > > We’re now beyond the honest mistake > > that a beginner would make and this qualifies as hostile since he was > > already warned and he created that branch to work around us. Can the > > release team give him back his training wheels, please? > > In last year debate, what I understood was that editing po/ files in > the main branches (“master” and “gnome-3-xx”) was causing problems, as > translators would not always be made aware of the change; here, what > I’ve done is with a completely different logic, as translators have > the final decision in the end, with every change. > Last year we haven't discussed about changes in other than the main branches, because it was not imagineable that you would open a backdoor some time later, using such a maintainer-only branch. Regarding the mentioned "different logic", it is your logic, and it is hard to understand. You've broken the simple rule "don't touch po files, and in return translators don't touch your source files" again. And by the way, the "final decision" is still yours, because you made the tarball release from your maintainer-only branch (as Jeremy Bicha already stated). But besides your logic, most of your "fixes" and "improvements" were senseless and absolutely uncritical for the release, and some of them have changed correct translations to incorrect ones. Is this your understanding of making things better, even better than the translation teams can do? Honestly, I didn’t imagined that translators would see something wrong > with me using this new workflow, This new workflow is no more than a cheap copy of the old one. I'm afraid you still haven't understand the problem... and I never thought of it as being > “hostile” or “to work around [translators]”. Of course, I will stop > pushing changed translations to users starting for now (and I hope I > understood correctly the problem this time; are we at least ok on the > words used?). > > Regards, > Arnaud > I hope you respect the rules now. But you have abused the trust of the Gnome TP members, you should be aware of that. Would be a good idea to keep an eye on your future activities. Best Regards, Mario > > -- > Arnaud Bonatti > > courriel : arnaud.bona...@gmail.com > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Unauthorized translation changes in dconf-editor
schrieb am Mo., 18. März 2019, 15:17: > Please keep gnome-i18n@gnome.org CCed > > On Mon, Mar 18, 2019 at 5:02 AM, Arnaud Bonatti > wrote: > > Hi Jeremy and Michael, hi release-team, > > > > 2019-03-17 17:01 UTC+01:00, mcatanz...@gnome.org > > : > >> I see: > >> > >> > >> > https://gitlab.gnome.org/GNOME/dconf-editor/commits/maintainer-only-3-32/po > >> > >> which seems pretty excessive. You probably wouldn't be very happy if > >> translators starting introducing unexpected changes outside of po/, > >> right? In the same way, the translators would prefer you to not make > >> changes under po/. > > > > That’s my role as a maintainer to ensure that the product that is > > taggued as stable does not look broken. > > > Your role as a maintainer doesn't include unauthorized changes of po files, which aren't approved by the translation teams and get released secretly via a "maintainer only" Git branch. As I already wrote one year ago: Never touch po files, really never! If you don't stop with your willful "fixes" and "improvements", we should consider to remove dconf-editor (and any other software maintained by you) from the Damned Lies pages. Best Regards, Mario > If translations are breaking the application layout, by translating > > the word “Translators” as something crediting translators on a > > long > > multiline string (the said “translator-credits” string from the > > About > > dialog), it’s my role to not tag a stable release without these > > translations fixed. > > > > If a translation contains a web link to what is currently an > > hypnotherapist website, it’s my role to remove that link before it > > hits the stable release. Even if I didn’t had the time to join the > > translator or its team to fix it in l10n. (Yes, it’s a true story. > > Not > > a big issue, but a real life one.) > > > >> Why is this necessary? They can't maintain their translations if you > >> have your own separate translations that never make it into > >> l10n.gnome.org. > > > > My goal is of course to upstream these changes is l10n, not to > > maintain a out of tree patchset indefinitely. > > > > But this upstreaming takes time: sometimes translators do not answer > > (see > > > https://bugzilla.gnome.org/buglist.cgi?quicksearch=product:l10n%20dconf-editor > > for long-time bugs without answers), sometimes translators take time > > to understand the problem, and I have to tag a stable release by the > > time. > > > > But that should not be a surprise if the last commit before the 3.32 > > dconf-editor release (8d0fa918) is fixing in one translation a problem > > I discovered and temporarily fixed in other po files, that’s part of > > my work with translators on these issues. > > > > As opposed to what Jeremy Bicha says, my current workflow is not > > breaking the translators one; that was not the case with my previous > > attempts (sorry again with that). And it is fixing translations for > > real life users. And that’s the important part of this story. > > > > Regards, > > Arnaud > > > > -- > > Arnaud Bonatti > > > > courriel : arnaud.bona...@gmail.com > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translations for Glabels 4.0
Hi Sveinn, Am Do., 1. Nov. 2018 um 10:58 Uhr schrieb Sveinn í Felli : > Hi, I'm really curious: > > Þann 1.11.2018 09:04, skrifaði Mario Blättermann via gnome-i18n: > > Dear translators, > > > > the po files for Glabels are maintained in the Damned Lies pages for more > > than ten years. Thanks for all your work on making Glabels better by > > translating it into many languages! > > About leaving DL: is it because translations were not up to expectations > or because DL insists on the PO/gettext format? Other? > We don't bother with quality or incompleteness of translations. I don't know whether DL supports ts files (even from an external repo), but I can't really imagine that it would. And a pure Qt project without any Gnome relations inside a pure Gnome/GTK translation management system ... could you imagine that? Doesn't make sense at all. > > > But Glabels development has been switched from GTK to Qt, and the version > > control system now resides at Github [1]. > > OK, your choice of a toolkit. Not much of a trouble for experienced > translators running lupdate back and forth to get files over to PO/POT > and thus being able to use a variety of tools (instead of being > restricted to Qt-Designer), but most projects I know who have gone this > route have suffered from severe loss of active translators. This is > something you're aware of, right? > > Maybe, but I've not made the decision to switch from Gettext to the native Qt format for translations. You are not restricted to Qtlinguist: Virtaal also understands this format. But even Qtlinguist has an advantage for me. When opening a ts file directly within a file hierarchy checked out from Git, I can view the appearance of a string in the GUI. > ... We have a new project at the Zanata translation management platform. > > > ... The Zanata platform doesn't support ca@valencia, so this po file > hasn't been imported. > > Why Zanata? > As I understand the situation, not a single commit has gone into their > code since beginning of September. Zanata is a RedHat product, which was > sort of pushed upon projects like Fedora - whose members are growling > and complaining about lack of features/support (and about loss of > translators). > Now, from this thread [1] (see last couple of posts), we can assume that > RedHat may have abandoned Zanata (and is itself en route of being bought > by IBM), which may lead to speculations about Zanata's future. But of > course it's your choice... > > Did you consider other translation platforms like Weblate, > Translatewiki, etc.? > > Please don't take my remarks as criticism, I'm just curious to know the > answer to these questions. > > [1]: > < > https://lists.fedoraproject.org/archives/list/tr...@lists.fedoraproject.org/thread/YDPRYFHRLKPFFABFCYF5ADHJNOAPU63W/ > > > > Zanata must not be the one and only final solution. And it doesn't matter when the Zanata code received the last commit. Well, the incomplete support for ts files is a bit annoying (bogus warnings about the & in strings which mark the mnemonics) but it works. And moreover, for those who prefer a local translation tool, downloading a file and uploading after translation works without problems. Regarding Weblate, I've tried to establish a Glabels translation project there. But after a few weeks I've got the answer from the Weblate people that Glabels doesn't seem to be a free software project in their understanding. They haven't had a look at the sources, what a shame. So I've decided to use Zanata for now. And last but not least, the development of the GTK based Glabels must not end here, if someone is willing to pick up the code. But I don't expect any future versions of Glabels v3.x from Jim Evins. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translations for Glabels 4.0
Hi Carmen, Am Do., 1. Nov. 2018 um 12:38 Uhr schrieb Carmen Bianca Bakker < car...@carmenbianca.eu>: > Hey Mario, > > On ĵaŭ, 2018-11-01 at 10:04 +0100, Mario Blättermann via gnome-i18n wrote: > > But Glabels development has been switched from GTK to Qt, and the > > version control system now resides at Github [1]. The upcoming major > > version 4.0 will be based on Qt. Along with the Qt port, we are no > > longer using po files, but ts files. > > Apart from Sveinn's fairly valid concerns, I am not really understanding > why the switch from gettext to Qt Linguist was made. Is it not possible to > keep using gettext (and keep all current infrastructure) while still > using Qt? I understand that it is not Qt's native solution, but it's > perfectly feasible. I know that KDE uses gettext instead of Qt > Linguist[1]. > > The decision to switch to the native ts format was made by the main developer Jim Evins. Maybe it is more simple to maintain within a pure Qt application. Don't forget, Glabels won't become a KDE app, the goal is to be platform-independent, see [1]. [1] https://github.com/jimevins/glabels-qt/issues/30 Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Translations for Glabels 4.0
Dear translators, the po files for Glabels are maintained in the Damned Lies pages for more than ten years. Thanks for all your work on making Glabels better by translating it into many languages! But Glabels development has been switched from GTK to Qt, and the version control system now resides at Github [1]. The upcoming major version 4.0 will be based on Qt. Along with the Qt port, we are no longer using po files, but ts files. We have a new project at the Zanata translation management platform [2]. If you are willing to continue translating Glabels, please create an account there. As far as it was possible, we have migrated existing translations from Damned Lies, the translation status is mostly around 30%. So almost all languages are still available, with one exception: The Zanata platform doesn't support ca@valencia, so this po file hasn't been imported. Note, we have split the translations into two files, the templates are now handled separate from the GUI. For the time being, we host only the GUI translations there. Once we have a user manual again, this will become also available for translation (probably also the man pages). [1] https://github.com/jimevins/glabels-qt [2] https://translate.zanata.org/project/view/Glabels Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Cannot commit into Gimp via DL
Hi Claude, Am Do., 20. Sep. 2018 um 09:04 Uhr schrieb Claude Paroz : > > Le 19.09.18 à 13:58, Mario Blättermann via gnome-i18n a écrit : > > Hello, > > > > since last sunday or so, I'm unable to commit po files to Gimp using > > DL. This affects two modules so far, but maybe the whole Gimp 2.10 > > branch: > > > > https://l10n.gnome.org/vertimus/gimp/gimp-2-10/po-plug-ins/de/ > > https://l10n.gnome.org/vertimus/gimp/gimp-2-10/po/de/ > > > > I get a "504 Gateway Timeout". Maybe the DL bot doesn't have the > > correct commit rights anymore...? > > Hi Mario, > > If the commit is not applied (check the repo), this is most probably > related to: > https://gitlab.gnome.org/Infrastructure/damned-lies/issues/76 > No, it was not applied. > In short, cheking out the branch from the Webapp process returns an > OSError(-25) with a SIGCONT or SIGXFSZ signal. This happens only on big > checkouts, most of the time Gimp but sometimes also with other modules. > This does not happen when manually running the same command in the > command line. Now I have commited the file directly via the Gitlab web interface. Best Regards, Mario > > If anyone has a clue about a possible resolution, you are welcome! > > Claude > -- > www.2xlibre.net > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: release notes not allowed translation
Hi Fabio, Am So., 2. Sep. 2018 um 10:48 Uhr schrieb Fabio Tomat via gnome-i18n : > > Don't know if I opened bug properly > but commiting from DL the translation to the release notes for GNOME 3.30 i > got this error > [Errno 128] Command: "['git', 'push', 'origin', 'gnome-3-30']", Error: > GitLab: You are not allowed to push code to this project. fatal: Could not > read from remote repository. Please make sure you have the correct access > rights and the repository exists. > Even my attempt to commit your translation directly from the Gitlab web interface failed: »You're not allowed to replace files in this project directly. Please fork this project, make your changes there, and submit a merge request.« So you filed your bug correctly, because at least the D-L bot should be able to commit. > Moreover I see that Friulian is not inserted to DOC_LINGUAS After committing the German translation, Piotr Drąg has changed the DOC_LINGUAS file accordingly. It needs to be done manually anyway. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Problem with the Pitivi manual in DL
Hello, recently I've updated the German translation of the Pitivi user manual. In the DL page, an error message appears: Error regenerating POT file for document pitivi-help: itstool -o /git/pitivi/help/C/pitivi-help.pot C/C/selectiongrouping.page C/C/layers.page C/C/workwithprojects.page C/C/splitting.page C/C/keyframecurves.page C/C/presets.page C/C/transitions.page C/C/mainwindow.page C/C/movearoundtimeline.page C/C/about.page C/C/index.page C/C/sysreq.page C/C/codecscontainers.page C/C/license.page C/C/gstreamer.page C/C/savescreenshot.page C/C/importingmpegts.page C/C/usingeffects.page C/C/medialibrary.page C/C/welcomedialog.page C/C/importing.page C/C/effects.page C/C/rendering.page C/C/trimming.page C/C/usingclips.page C/C/cheatsheet.page Error: cannot open XML file C/C/selectiongrouping.page The mentioned file is present. What's the problem here? I could imagine a general problem with all XML files, but only the first one will be issued (because itstool stops at failure). The file path patterns C/C/foo.page (with the duplicate C/) are strange, maybe there's something wrong in the Meson workflow, or in the itstool scripts in Vertimus? Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Issues with DL
Daniel Șerbănescuschrieb am So., 25. März 2018, 21:01: > Hello I experience some issues with encoding while committing on DL. > I tried to commit the latest file from : > https://l10n.gnome.org/vertimus/gnome-maps/master/po/ro and was unable to > commit from Damned Lies. > > The error reads: > > 'ascii' codec can't encode character '\u0218' in position 7: ordinal not > in range(128) > > How can I find out what is wrong with the file? I tried to commit via git > but now the words stats are broken in Damned Lies. > Any Ideas? > There is probably nothing wrong with your file. Yesterday I tried to commit three different files, and all of them failed with an error message similar to yours. It's rather an issue in DL itself. Cheers, Mario > ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: yelp appdata file
2018-03-24 10:32 GMT+01:00 Alexandre Franke: > On Fri, Mar 23, 2018 at 4:59 PM, Kalev Lember wrote: >> Hi, > > Hi, > >> I went ahead and pushed an appdata file for yelp to git and didn't >> branch yelp for 3.28 before that. I hope it's ok, as it's basically >> fixing untranslated strings in gnome-software (almost all downstreams >> were already shipping untranslated appdata files as downstream patches). > > This seems to fall under the “marking unmarked strings” case anyway, > so I don’t think you need approval (but the heads is appreciated!) > >> piotrdrag +1'd the plan on IRC and Daniel Mustieles said in 2014 that >> this has +1 from the i18n team :) > > Exceptions are granted by the i18n team for a given branch at a given > time and one shouldn’t rely on a 4 year old nod in the general case. > Indeed, in such cases an exception is always needed, we can't grant an exception for a "group" of cases, if we don't want to lead our freezes system to absurdity. @Kalev: Here you shouldn't speak about a case of "marking previously unmarked strings as translatable". The appdata file didn't exist yet, it has been newly added. Doesn't matter what downstream packagers do, we should always refer to our Git content. In any case, someone has to ask for a freeze exception *before* pushing changes, additions, whatever. Doesn't make sense to write a message after making the changes, hoping it's OK. And in this particular case, adding an appdata file is far from fixing a critical bug, which would justify a freeze break. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gitlab access for translators
2018-03-10 14:25 GMT+01:00 Alexandre Franke <afra...@gnome.org>: > On Sat, Mar 10, 2018 at 12:40 PM, Mario Blättermann > <mario.blaetterm...@gmail.com> wrote: >> >> Hi all, > > > Hi, > >> >> recently GNOMe has switched to Gitlab. Don't know the reasons, but >> don't matter at all... Now I have a problem. I have write access in >> the original GNOME Git for ages, and I can still checkout a module >> using my user name and SSH key. But when I like to write changes back, >> I get an error message that I have to use Gitlab from now on. The wiki >> page [1] doesn't give me any instructions how to do so and lists the >> old commands only. > > > People who used to have access to git still have access to git repos on > gitlab. You may have to login once through the web interface, and wait for > the next puppet run (once every hour), to activate something. Then you > should be good. The warning may also indicate that you need to use a > different URL for cloning, but push access won’t be removed with the > migration. > Thanks for the hint. Indeed, it works again. But it should be considered to update the wiki pages... Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Gitlab access for translators
Hi all, recently GNOMe has switched to Gitlab. Don't know the reasons, but don't matter at all... Now I have a problem. I have write access in the original GNOME Git for ages, and I can still checkout a module using my user name and SSH key. But when I like to write changes back, I get an error message that I have to use Gitlab from now on. The wiki page [1] doesn't give me any instructions how to do so and lists the old commands only. Usually translators don't need real write acess anymore, because the Damned lies pages allow to commit translations directly. But in a few cases, this doesn't work: Creating new po files which don't exist yet, images for manual translations, changes in help/Makefile.am... So it is still needed to keep the git access alive also for translators. [1] https://wiki.gnome.org/Git/Developers#Developer_Access Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [dconf-editor] cleaning of translations, 2nd approach
2018-03-06 21:54 GMT+01:00 Rafal Luzynski <digitalfr...@lingonborough.com>: > 6.03.2018 21:33 Mario Blättermann <mario.blaetterm...@gmail.com> wrote: >> [...] >> Who is "one" in this case? Who makes the decision that it's okay to >> throw other's work away? [...] > > A project maintainer/developer? I don't know. I'm not telling that > one should remove the files but just in case if someone find them > not useful enough. There are lots of cases, including the extreme ones > where only 1 or 2 strings are translated. > Before removing such a sparse po file, it is recommendable (rather mandatory) to contact the responsible translation team. And only in case the team doesn't exist anymore or nobody responses within a reasonable time frame, the file could be removed without any extra approval. But as I already wrote, I'm in doubt of the benefit of such an action. Maybe to get the "global control" of the project back again...? Don't know. >> In general, I'm in doubt about the benefit of your plans. > > This is not my plan. Of course, this refers to Arnaud's plans, not yours. Not to forget, instead of bothering with such rather cosmetic things, developers could help us to make our translations better by placing as many translator comments as possible. Well, the situation has significantly improved over the years, but there's still a lot to catch up. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [dconf-editor] cleaning of translations, 2nd approach
2018-03-06 20:55 GMT+01:00 Rafal Luzynski <digitalfr...@lingonborough.com>: > 6.03.2018 14:09 Arnaud Bonatti <arnaud.bona...@gmail.com> wrote: >> [...] >> 2018-03-06 13:47 UTC+01:00, Mario Blättermann <mario.blaetterm...@gmail.com>: >> > Never touch po files, really never. […] >> >> I don’t find a way to express how sad I am to see that it looks >> impossible for devs to help translators in other way than adding >> things to translate; and for maintainers to have a global control of >> the product they maintain. [...] > > I'm not sure how Damned Lies works but don't the project developers > or maintainers have the power to contribute to any translation (in > any language) for their projects? > > Back about your idea: I'm afraid it does not make much sense because > your removed strings would be restored in the next translation update. > Same about your updates which would be overwritten by the content > of Damned Lies, no matter if the content is newer or older. And, finally, > if the string is no longer used then it would be removed anyway so > your patch does not do anything that Damned Lies would do, if used > properly. Damned Lies doesn't remove unused strings at all. They remain after the underlying Vertimus tool has merged the po files with the latest generated POT template (without any real changes in the git repo). Translators can then decide to remove them, or not. Unused strings can help to find a good translation for another string. Well, nowadays the GUI tools like Poedit do this work using their translation memory. But you must not expect that just everyone works with specialized GUI editors. Maybe some (or some more, who knows...?) people prefer simple text editors, and in that case the unused strings can become very helpful. > > In the extreme cases, if the translation is too incomplete and > unmaintained for too long one may consider removing the language > from the project. Who is "one" in this case? Who makes the decision that it's okay to throw other's work away? A po file doesn't eat up that much disk space, and as long as it doesn't break things, keep it as is. In general, I'm in doubt about the benefit of your plans. A shrinking of 3,3% of the tarball size is no real benefit. A (maybe) better workflow for grep is no real benefit. With some clever grep calls, it doesn't matter how big or "trashed" a file is. And last but not least, you won't benefit from removing old and unmaintained po files, because they don't cause extra work for you. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [dconf-editor] cleaning of translations, 2nd approach
2018-03-06 14:44 GMT+01:00 Ask Hjorth Larsen: > [...] > Changing the subject to something purely practical: Pruning/cleaning > the po-files can probably be fully scripted, so there would be no harm > in committing a script somewhere which does this, then sending bug > reports to translation teams without actually committing the cleaned > po files. This would be a practical solution. It's only important to don't touch po files directly, that's all we expect. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [dconf-editor] cleaning of translations, 2nd approach
Hi Arnaud, Am 06.03.2018 11:32 schrieb "Arnaud Bonatti": Hello everybody! As you already know, I’m trying these days to improve the content of the “po” directory in the “dconf-editor” module I maintain. With the previous discussion in mind, let me summarize our rules: Never touch po files, really never. Even in the cases you feel there's something to improve or you are a native speaker of that language. If a po file breaks the build of your application, use this mailing list or bugzilla. In return, you may expect that no translator touches your source files, only in cases when a new translation comes up (such as help/Makefile.am or po/LINGUAS). Best Regards Mario (German translator for ages) ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: documentation translations
2017-09-20 20:18 GMT+02:00 Piotr Drąg <piotrd...@gmail.com>: > Hi Mario, it seems that your message didn’t go to the mailing list. :) > > 2017-09-20 19:25 GMT+02:00 Mario Blättermann <mario.blaetterm...@gmail.com > >: > > [...] > > I found a pending translation for the gnome-photos manual, committed it > to > > both master and gnome-3-26. > > > > Cheers, > > Mario > > > > -- > Piotr Drąg > https://piotrdrag.fedorapeople.org Thanks for forwarding! Sometimes I'm not aware of what the mailer does... Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: DOC_LINGUAS
Am Montag, 28. November 2016 12:30:35 CET schrieb Hannie Dumoleyn: Hello, I adding the Dutch translation of 'Gnome-getting-started-docs', see [1]. I created a folder \gnome-help\nl and copied the translation to this folder. I should have added nl to DOC_LINGUAS, but I cannot find it in \gnome-getting-started-docs. Can anyone tell me where I can find DOC_LINGUAS? You'll find it in gnome-help/Makefile.am. But note, it is HELP_LINGUAS, not DOC_LINGUAS. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gnome-Commander 1.6 to be released on September 26th, 2016
2016-08-22 22:14 GMT+02:00 Uwe Scholz: > Hi Translation Teams, > > Gnome Commander 1.6.0 is planned to be released on September 26th. For > your convenience, no strings will be changed up to this date. (*) > > Some changes and updates were made in the documentation. The Gnome > Commander application itself contains lot of new translatable strings. > > All translations completed prior to September 26th will be included in > this release. Your translation efforts are very much appreciated. > > > Thanks to all contributers! > > > Sincerely, > Uwe Scholz > (Maintainer of GNOME-Commander) > Thanks for the info! For the convenience, here's the current translation state: https://l10n.gnome.org/module/gnome-commander/#master > (*) On this date we will create a new "gcmd-1-6" branch. Branches with > lower version numbers are then obsolete for new translations. OK, once you've created that branch, we will update the Damned Lies pages. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: About translating GIMP website (gimp.org)
2016-05-30 0:41 GMT+02:00 Alexandre Franke: > On Sun, May 29, 2016 at 8:28 PM, Jehan Pagès > wrote: >> So would this be possible? If this is all good, and once we get all >> our text as po files, what is the next step to subscribe the GIMP >> website as a GNOME i18n project and get the ball rolling for >> internationalization? :-) > > I'll let the others weigh in now. > It is possible using po4a, as already mentioned, and you don't have to bother with po files at all. All we need is an up-to-date template (*.pot). Merging it into existing po files is done by or Vertimus tool. In our current workflow, Vertimus is monitoring the Git commits. Each time an appropriate Git commit happens, the pot file will be updated and merged into the po files for each language. This works perfectly for translations based on intltool (GUIs) and yelp tools (docs). For po4a it doesn't work out-of-the-box, but possibly can be done with a custom script. I expect a lot of translatable strings and accordingly a lot of work for translators. I urgently recommend to split the content into smaller chunks, preferably according to the directories in the Git module [1]. There is also a "man" directory included, so we would get also translated man pages. Some notes about po4a itself: The Markdown module is not perfect. In some cases, translators will get annoying gettext strings which contain only underlinings and some other formatting stuff. In any case we need to provide extra information for translators what they have to keep in their translations to don't break the generation of the localized version. Moreover, by default po4a doesn't accept po files which have less than 80 % of the source strings translated, based on the pure count of gettext strings. Translators should get informed about that. Well, this percentage could be screwed down in the po4a configuration, but I prefer a translated website without gaps or at least only with a few gaps, so we should keep it at 80%. As far as I know, po4a cannot handle "translated" pictures, as known from our DocBook or Mallard manuals. There's some extra work needed to handle translated pictures. [1] https://git.gnome.org/browse/gimp-web/tree/content Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Strange string in Damned Lies translation
Hi all, while translating the po file for the Damned Lies website, I found this string: #: templates/vertimus/vertimus_detail.html:179 #: templates/vertimus/vertimus_detail.html:185 msgid "Y_g_i_s" msgstr "" What's the meaning of this and where can I found it in Damned Lies? Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New file-roller translation
Am 14.04.2016 um 14:48 schrieb Rafael Fontenelle: > Interlingua team exists [1]. The original poster informed the language > code 'ie', however the correct is 'ia' in the ISO 639 [2]. > Interlingua (ia in ISO 639-1) and Interlingue (ie) are not the same. >From https://en.wikipedia.org/wiki/Interlingua: Not to be confused with Interlingue, Interlanguage, or Interlingual machine translation. This article is about the auxiliary language created by the International Auxiliary Language Association. And from https://en.wikipedia.org/wiki/Occidental_language: Not to be confused with Interlingua or Occitan. The language Occidental, later Interlingue, is a planned international auxiliary language created by the Balto-German naval officer and teacher Edgar de Wahl, and published in 1922. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New file-roller translation
Hi Alexa, Am 13.04.2016 um 19:35 schrieb -скрыто- Алекса: > OK, here's the not reduced file. > > There's no team for "ie" on the localization site. then the team has to be created. But first let's have a look at the file header: # kk@latin translation for file-roller. This refers to a Kazakh translation, please change it to Interlingue (preferred the full word). # FIRST AUTHOR, YEAR. Please fill in your full name, mail address and year. "Plural-Forms: nplurals=2; plural=(n!=1);\n" I haven't found anything on the web about plural forms in Interlingue, as long as it is the same as in Interlingua, this line should be OK. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gspell: new branch
Am 06.04.2016 um 12:16 schrieb Sébastien Wilmet: > Hi, > > The gspell-1-0 branch has been created: > https://git.gnome.org/browse/gspell/log/?h=gspell-1-0 > OK, I've changed "gspell-0-1" to "gspell-1-0" in "Extra GNOME Applications (stable)" in the Damned Lies pages. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Commit PO file into git
Hi Daniel, Am 30.03.2016 um 09:27 schrieb Daniel Mustieles García: > Hi all, > > I'm not able to commit this file directly from DL, and these days I will > have limited access to my ssh key, so I wanted to ask you if someone > could commit this PO file into git for me. > > It's an updated translation of the video-subtitles module > (https://l10n.gnome.org/vertimus/video-subtitles/master/gnome320/es) > > Thanks in advance for your help :) > Done. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Odd tab in a translatable string in sound-juicer
Hi Alexandre, Am 22.03.2016 um 12:18 schrieb Alexandre Franke: Hi, On Tue, Mar 22, 2016 at 11:41 AM, Mario Blättermann <mario.blaetterm...@gmail.com> wrote: #: ../src/egg-play-preview.c:229 #, fuzzy #| msgid "The duration of the current stream in seconds." msgid "The duratio\tn of the current stream in seconds." msgstr "Die Dauer des momentanen I don't see the issue in https://l10n.gnome.org/POT/sound-juicer.gnome-3-18/sound-juicer.gnome-3-18.de.po Indeed, it is vanished... Maybe a temporary stumble in Vertimus or anything similar ;) But believe me, it was there! The appropriate string was in all languages which were at 100% previously. OK, sorry for the blurb, but it was worth for me mentioning here. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Odd tab in a translatable string in sound-juicer
Hi Phillip, some minutes ago the translation template of sound-juicer (3.18 branch) has been changed automatically and the Damned Lies page shows it with one fuzzy string: #: ../src/egg-play-preview.c:229 #, fuzzy #| msgid "The duration of the current stream in seconds." msgid "The duratio\tn of the current stream in seconds." msgstr "Die Dauer des momentanen Audiodatenstroms." I assume it is not intended to have a tab inside the word "duration". Don't know how this has happened, I don't see any peculiarities in the latest commits there. Any idea? CC'ing the gnome-i18n list, maybe someone knows some more about it. BTW, it is only in 3-18, not in the master branch. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: 3.20 release notes available for translation
Am 16.03.2016 5:17 nachm. schrieb "Frederic Peters": > > Hi, > > Allan Day wrote: > > The text of the 3.20 release notes is now done and is ready to be > > translated. There are some missing screenshots: we'll try and get > > those included as soon as possible. The release notes can be found in > > the usual place: > > > > https://git.gnome.org/browse/release-notes/log/?h=gnome-3-20 > > > > The release is scheduled for 23rd March, which is one week from today. > > > > Just let me know if you have any questions, or if you spot any problems. > > And I just enabled https://help.gnome.org/misc/release-notes What are username and password? Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gtk+ statistics doesn't get updated in damned lies
May we expect to get fixed this within a reasonable time frame? I don't really know the possible reasons of splitting po and po-properties in two modules. The old behavior worked perfectly over the years, why not get back to the old one? Best Regards, Mario Am 17.03.2013 08:19, schrieb Kenneth Nielsen: Me to me to (Danish) 2013/3/15 Aurimas Černius auri...@gmail.com: Hi, For Czech Gtk+ too. Lithuanian stats are not updated too... -- Aurimas ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-getting-started-docs video translation
Am 19.03.2013 00:43, schrieb Petr Kovar: On Mon, 18 Mar 2013 23:31:46 +0100 Petr Kovar pk...@volny.cz wrote: Yes, you can get the translated SVGs by building the tarball, see above. Simply run yelp . in gnome-help/de/ to display the translated Mallard document with included SVGs. Actually, the command you need to run in gnome-help/de/ is: yelp getting-started.page This is because yelp . expects an index.page file, but this file is already installed with gnome-help from gnome-user-docs, so we can't install it with getting-started. OK, it works so far. I've just downloaded the tarball v3.7.92, and it contains the translated SVG files. But what about translated webm animations? They are missing from the tarball and Yelp shows empty player frames only. I've seen it Git, the webm files are included in the figures subfolder for the Czech language. Do I have to pre-create them also for German, or is this a task for the distribution packagers (by the make toolchain)? Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gtk+ statistics in damned lies don't get updated
Am 13.03.2013 12:33, schrieb Fran Dieguez: Hi all, a couple of hours ago I have updated the gtk+ ui and properties translations for the Galician language but seems that Damned lies refuses to update that module in particular. https://l10n.gnome.org/languages/gl/gnome-3-8/ui/ https://git.gnome.org/browse/gtk+/log/?h=gtk-3-8 Can you take a look at it? See the bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=695009 https://bugzilla.gnome.org/show_bug.cgi?id=695528 https://bugzilla.gnome.org/show_bug.cgi?id=686027 Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Nautilus folder names
Am Donnerstag, 14. Februar 2013, 02:33:16 schrieb Chynggyz Jumaliev: On 14.02.2013 02:19, Enrico Nicoletto wrote: Hello Chynggyz. You have to translate them in compliance with the same traduction that was used to translate the system´s folder. For instance, in Brazilian Portuguese, they are: Fotos, Vídeos, Modelos, Downloads Kindly regards Em 13/02/2013 18:12, Chynggyz Jumaliev escreveu: Hi, how can I translate the folder names from Nautilus, e.g. Pictures, Videos, Templates, Downloads etc. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n Sorry, I meant to ask in which file I can translate this words. These folder names are not translatable in Gnome itself. The translated strings are fetched from xdg-user-dirs, which is maintained at translationproject.org [1]. Best Regards, Mario [1] http://translationproject.org/domain/xdg-user-dirs.html ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'folks.master'
Am 07.11.2012 20:09, schrieb Piotr Drąg: 2012/11/6 GNOME Status Pages nore...@gnome.org: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'folks.master': + My Contacts is only available for Google Contacts Hello once again. :) Could you please switch folks to folks-0-8 branch? Done. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: incorrect missing vte branches
Hi Christian, Am 02.10.2012 21:13, schrieb Christian Persch: Hi; I just noticed at http://l10n.gnome.org/module/vte/ that i18n is apparently using the wrong vte branches: - master is *NOT* string frozen - the vte-0-34 branch that is string-frozen and used for gnome 3.6, is missing - the vte-0-32 branch for gnome 3.4 is missing as well, but that's not so important since there'll be no more releases from it. Note for translators: it's absolutely *no use* translating vte master since there will be no releases from it; translate vte-0-34 (and vte-0-36 once it exists). Thanks for that info. I've just fixed both it in the status pages. However, it would be nice to get such information before we go into the string freeze. No one of us is continuously tracking all the branch creations in Git. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gedit string change (desktop file keyword)
Am 09.09.2012 12:31, schrieb Paolo Borelli: Hi, we recently added a keyword to the gedit .desktop file, but it was pointed out that it needs to be translated. Can we apply the patch in bug https://bugzilla.gnome.org/show_bug.cgi?id=683610 +1 from i18n. It's a kind of existing string which wasn't marked for translation yet, that's why actually no freeze break. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'alacarte.master'
Am 17.07.2012 19:38, schrieb Jasper St. Pierre: On Tue, Jul 17, 2012 at 1:10 PM, Gil Forcada gforc...@gnome.org wrote: El dt 17 de 07 de 2012 a les 12:52 -0400, en/na Jasper St. Pierre va escriure: On Tue, Jul 17, 2012 at 12:17 PM, Gil Forcada gforc...@gnome.org wrote: El dt 17 de 07 de 2012 a les 00:26 +, en/na GNOME Status Pages va escriure: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'alacarte.master': + Restore System Configuration Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. http://git.gnome.org/browse/alacarte/log/?h=master Hi Jasper, Seems you broke the GNOME 3.4 string freeze with you commit on alacarte: http://git.gnome.org/browse/alacarte/commit/?id=6517d363de24299b5472ba43d0af7396fcb9e086 Would you mind creating a GNOME 3.4 branch before that commit? Done. I don't see the point in creating a GNOME 3.4 branch, but sure, done. The point is to not add strings to already released modules, that's what a string freeze is for :) Just like developers fix bugs, we translators, fix any string pending to be translated, that's why new branches are for. To prevent new strings to pollute those statistics, which will only bring confusion to translators and users. Well sure, but there isn't going to be another gnome-3-4 release, so why bother making a branch for it? Cheers, Cheers, -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net -- Gil Forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net planet: http://planet.guifi.net Just FYI, the gnome-3-4 branch of alacarte resides now in GNOME 3.4 (stable) but the master branch remains in Extra GNOME applications. Shouldn't the latter go back to the GNOME 3.6 (development) release set? I don't know about the reasons why it has once been gone, but seems that it should be a part of the core modules. However, I haven't take a look at the jhbuild modules... What's the current state? Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Confirming Piotr Drąg as the new coordinator for the Polish team
Am 09.07.2012 09:06, schrieb Tomasz Dominikowski: Hi, I'm the current coordinator for the Polish team and I'd like to confirm that Piotr Drąg is the new coordinator for the Polish team. Please perform all the relevant administrative tasks in Damned Lies, etc. to move forward. The Polish team has never been in better hands, with a dedicated coordinator who eats his own dogfood. I couldn't continue with the role as I have moved on to using different software solutions. Good luck Piotr! Regards, Tomasz Dominikowski Coordinator has been changed as desired. Piotr, you should be able now to do some maintenance when you login at your team page, such as mark translators as commiters and so on. Good luck with your new job! Best regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New coordinator for Polish team
Am 03.07.2012 19:52, schrieb Piotr Drąg: Hi, I'd like to inform you that I've taken over the coordinatorship of Polish translation team from Tomasz Dominikowski. Unfortunately, he is too busy with his day job to inform you in person, but I can assure you that he approves this change. I'll ask him to confirm this mail as soon as possible. As for who I am, you should probably know me, as I am the sole Polish translator for past few releases. :) I already have git account. I also try to help with various localization bugs/tasks/activities, such as keeping POTFILES.in up to date, finding and fixing untranslatable strings, removing mark-up etc. I'm also the maintainer of Fedora Polish translations, as well as many other minor and major projects. I would like to become the coordinator in Damned Lies and the default asignee in Bugzilla, so could you tell me what steps should I take? Best regards, You haven't to do anything. Once the confirmation from Tomasz Dominikowski has been arrived, a member of the i18n coordination team will change the coordinatorship in Damned Lies. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: goobox branched
Am 03.06.2012 16:28, schrieb Paolo Bacchilega: Hello, I've created the goobox-3-0 branch for the goobox git module. The master branch will be used to develop the new version, while goobox-3-0 will be used for maintenance of the 3.0.x series. Thanks for the information. I've added the goobox-3-0 branch to the Extra GNOME apps stable release set in Damned Lies. -Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-bluetooth.master'
Am 06.05.2012 23:47, schrieb GNOME Status Pages: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-bluetooth.master': + %d kB/s + ADDRESS + NAME + [FILE...] Just FYI, these strings were already present, but not marked for translation yet: http://git.gnome.org/browse/gnome-bluetooth/diff/sendto/main.c?id=063ee7827391cfabffe907d0ea1e33380ab4c47b Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-packagekit.gnome-3-0'
Am 01.05.2012 07:32, schrieb GNOME Status Pages: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-packagekit.gnome-3-0': + Allow applications to invoke the codec installer + Allow applications to invoke the codec installer. + Allow applications to invoke the font installer + Allow applications to invoke the font installer. + Allow applications to invoke the mime type installer + Allow applications to invoke the mime type installer. + Ask the user if additional packages should be installed + Ask the user if additional packages should be installed. + Ask the user if files should be copied to a non-private directory when installing from a FUSE mount. + Ask the user if files should be copied to a non-private directory + Automatically remove unused dependencies + Filter package lists using basename in gpk-application. + Filter using basename in gpk-application + GTK+ module for font installation + If search terms should be completed automatically + If search terms should be completed automatically. + Notify the user before a large update is done on a mobile broadband connection + Notify the user before a large update is done on a mobile broadband connection. + Only show native packages in the file lists + Only show native packages matching the machine architecture in the file lists. + Only show the newest packages in the file lists + Only show the newest packages in the file lists. + Only show the newest packages in the update list, and filter out older updates that are still available. + Only show the newest updates in the list + Programs that should be ignored when they issue session D-Bus requests + Programs that should be ignored when they issue session D-Bus requests, separated by commas. + Scroll to packages as they are downloaded + Scroll to packages in the update list as they are downloaded or installed. + Show all repositories in the software source viewer + Show all repositories in the software source viewer. + Show the 'All Packages' group menu + Show the all packages menu item. This takes a long time to populate on most backends and is not generally required by end users. + Show the category group menu + Show the category group menu. This is more complete and custom to the distribution, but takes longer to populate. + The search mode used by default + The search mode used by default. Options are \name\, \details\, or \file\. + This key determines if applications should be able to prompt for fonts. + When displaying UI from a session DBus request, automatically use these options by default. + When displaying UI from a session DBus request, force these options to be turned on. + When removing a package, also remove those dependencies that are not required by other packages. Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. http://git.gnome.org/browse/gnome-packagekit/log/?h=gnome-3-0 What could be the reason for these string additions? I couldn't find anything in the recent Git commits, neither in gnome-packagekit itself nor in damned-lies. A bug in the latter, which has triggered the status reload by accidence? Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-packagekit.gnome-3-0'
Am 01.05.2012 14:36, schrieb Andre Klapper: On Tue, 2012-05-01 at 13:41 +0200, Mario Blättermann wrote: What could be the reason for these string additions? I couldn't find anything in the recent Git commits, neither in gnome-packagekit itself nor in damned-lies. A bug in the latter, which has triggered the status reload by accidence? http://git.gnome.org/browse/gnome-packagekit/commit/?h=gnome-3-0id=63d19e3f7b9043ae07cf26257c14309f266955bc seems to be a good explanation. andre OK, that's it. At the time I posted my question, this commit wasn't present in the Git web interface yet. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: kyrgyz language
Am 16.04.2012 20:27, schrieb chingis: I want to translate the Gnome, but there are no any active members. How can I begin to translate and commit. Do you've tried to contact the current coordinator Timur Jamakeev ky...@mail.ru? If he doesn't response within two weeks or so, we should consider him as really inactive. Then you could become the new team coordinator. However, you are a member of the team and you are able to upload your translations to the appropriate modules. As long as you are the one and only translator, it shouldn't be a problem to commit them to the Git repo by one of us. Once you have contributed some translations (don't know what some means in particular here) you should try to get your own Git account. Just a technical issue: Don't use the function Write a comment in the Damned Lies statistics pages. As a translator, you have to use first Reserve for translation and then Upload the new translation. Besides that (assuming you want to become the coordinator), you can assign yourself to the Committers group in your team to make your translation available for committing. Once this has been happened, please inform this mailing list so that one of us can commit your file. Last but not least, it would be nice to know your full name. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: kyrgyz language
Am 16.04.2012 21:58, schrieb Bahodir: Welcome to Gnome! Follow this link: https://live.gnome.org/TranslationProject It has all the information you need. Bascially, you want to apply for the team coordinator position first. Once you are the coordinator, you can push your changes to git. No, not right. Team coordinators don't get their Git accounts automatically. They have to contribute some (or some more) translations first. In my case - some years ago - I have translated approximately more than 2000 strings before. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'libgdata.master'
Am 02.04.2012 17:37, schrieb Philip Withnall: On Mon, 2012-04-02 at 17:13 +0200, Andre Klapper wrote: On Mon, 2012-04-02 at 14:33 +, GNOME Status Pages wrote: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'libgdata.master': + Error received from server after uploading a resumable upload chunk. pwithnall libgdata master shouldn't be string frozen — it's unstable pwithnall The latest stable release of libgdata is 0.10.x pwithnall i.e. the libgdata-0-10 branch I've just branched libgdata for 0.12 (libgdata-0-12 branch) from just before I broke string freeze in master. Therefore, the latest stable release of libgdata is now 0.12.0. The libgdata-0-12 branch should be used for GNOME 3.4 translations, and master for GNOME 3.6. Philip OK, I've assigned libgdata-0-12 to the GNOME 3.4 release set. But there remain some untranslated strings for GNOME 3.0 and 3.2, because we have the master branch still there. What to do here? Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Special request for priority
Am 23.03.2012 09:46, schrieb Chris Leonard: On Fri, Mar 23, 2012 at 3:17 AM, Rudolfs Mazurs rudolfs.maz...@gmail.com wrote: C , 2012-03-22 18:00 -0400, Chris Leonard rakstīja: I would like to ask the various teams to consider prioritizing WebKitGTK+ for translation http://l10n.gnome.org/module/webkit/ Why isn't webkitgtk+ in at least gnome-extras category? Good question. Good answer: Webkitgtk+ is not available from the GNOME Git repo. Those modules are easy to maintain for translators, but supplying translations for Webkitgtk+ is some more difficult. First, you have to translate it, then you have to file a bug against Webkitgtk+, and one day (or some days later) you get the answer from the maintainers that your po file has been committed. In the meantime, your translation became outdated again. Not that attractive for translators, and not that practical. Due to these delays in the workflow, and due to that we don't have direct commit access anyway, it would be odd to recognize Webkitgtk+ as a normal module which could be assigned to a normal release set. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What happened to the follwoing obsolete packages
Am 13.03.2012 21:23, schrieb Alexander Shopov (Александър Шопов): Hello everybody, I am doing a little housekeeping for the Bulgarian Gnome Translation team Subversion repository. We have the following orphaned modules: deskbar-applet.master.bg.po eel.master.bg.po gail.master.bg.po gnome-build.master.bg.po gnome-mag.master.bg.po gnome-netstatus.master.bg.po gnome-system-tools.master.bg.po gnome-vfs.master.bg.po gok.master.bg.po lsr.master.bg.po swfdec-gnome.master.bg.po All of them are obsolete and some of them no longer can be found in http://l10n.gnome.org/module/ Most of them are so obsolete that they are no longer even in obsolete release set: http://l10n.gnome.org/languages/bg/obsolete/ui/ Still - these have been part of some GNOME release in the past, and I would like to keep the translated strings for reference. Is there another special place I can look at to guess what happened to these modules? You can found all the archived modules in http://git.gnome.org/browse/archive/. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-online-accounts.master'
Am 13.03.2012 21:34, schrieb Frederic Peters: GNOME Status Pages wrote: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-online-accounts.master': + quot;Use forquot; For reference, this happened after the module was branched for 3.4, it's just that damned-lies hasn't been updated yet. Update is done: http://l10n.gnome.org/module/gnome-online-accounts/#gnome-3-4 Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Confusion over epiphany new name
Am 11.03.2012 17:47, schrieb Abderrahim Kitouni: 2012/3/11 Ru-dolfs Mazurs rudolfs.maz...@gmail.com mailto:rudolfs.maz...@gmail.com Hello! It seems that Epiphany, the browser, is gradually being renamed to Web. If I understand correctly, this is because a typical user has no idea what Epiphany does. But for translators this is problematic. 1. When I go to Web's About page, I see pearls like Web Website and Copyright 2003-1012 The Web Developers. My language doesn't use articles, so the translations would be equivalent to Website of the Web and Copyright 2003-1012 Web developers. One of our translators also had the same problem with Contacts. Since this seems to be the direction gnome applications are going, it would be really nice to have some global policy on how to handle these. In any case, some consistency and clear expectations would be nice. Consistent options would be: a) replace the application name with the functional label (Files, Documents, Web) only in some predefined locations, and translate the new label (this is what I would prefer); This would be nice, but the new applications (e.g. Contacts, Boxes) don't have any other name. The global question is for me: Shouldn't we may expect that users (even the users at the lowest imaginable level) are able to remember some application names? In my mind, there's no plausible reason to throw the application names away. And as we see, this produces more problems than we had ever expected. In case of Epiphany, we display it in the menu as Web, just as Web would be the one and only web browser all around. But if we have a look at http://www.gnome.org/gnome-3/, the pictures show the Firefox logo within the dash (which is the default and widely used browser anyway). I don't believe that we get more Web users this way. Epiphany is quite far from being (or becoming) _the_ web application. However, it is not the place here to discuss such basic things, but I'm sure here are some (or perhaps some more) people who can follow my thoughts. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [Glade] Created branch glade-3-12
Am 20.02.2012 21:46, schrieb Juan Pablo Ugarte: Hi guys, I just created a Glade stable branch for GNOME 3.4 named glade-3-12 Just added it to the D-L pages, but we need a weighted sort order (as in the glabels module some months ago). The branch appears as expected in the 3.4 release set, but it is the last one in the module overview and collapsed. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Fwd: String additions to 'gnome-disk-utility.master'
Hi David, your recent commits to the gnome-disk-utility Git repository break the string freeze for GNOME 3.2, because there's no branch for gnome-3-2 yet. Please branch for gnome 3.2 in an earlier stage. Best Regards, Mario Original-Nachricht Betreff: String additions to 'gnome-disk-utility.master' Datum: Fri, 20 Jan 2012 21:49:43 - Von: GNOME Status Pages nore...@gnome.org An: gnome-i18n@gnome.org This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-disk-utility.master': + %d span size=\small\(Worst:%d, Threshold: %d)/span + %d hour + %d hours + %d minute + %d minutes + %d msec + %d second + %d seconds + %s (%s) + %s span size=\smaller\(Read-Only)/span + %s Block Device + %s Loop Device + %s ago + /etc/crypttab configuration data is malformed + A file named \%s\ already exists. Do you want to replace it? + All Files + All data on the partition will be lost + All data on the volume will be lost + All existing data will be lost + Are you sure you want to format the disk? + Are you sure you want to write the disk image to the device? + Cannot create a new partition. There are already four primary partitions. + Cannot restore image of size 0 + Changing the passphrase for this device, will also update the passphrase referenced by the i/etc/crypttab/i file + Compatible with Linux systems + Compatible with all systems and devices + Compatible with modern systems and hard disks 2TB + Compatible with most systems + Copying data from device i%s/i... + Copying data to device i%s/i... + Custom + DISK IS LIKELY TO FAIL SOON + Description + Disk Drives + Disk Image of %s (%s).img + Disk Images (*.img, *.iso) + Disk is OK, one attribute failed in the past/Disk is OK, %d attributes failed in the past + Disk is OK, one bad sector/Disk is OK, %d bad sectors + Disk is OK, one failing attribute is failing/Disk is OK, %d attributes are failing + Disks + Encrypted, compatible with Linux systems + Enter filesystem type + Error aborting SMART self-test + Error adding /etc/crypttab entry + Error adding new /etc/fstab entry + Error attaching disk image + Error changing passphrase + Error deleting loop device + Error determing size of file + Error determining size of device + Error ejecting media + Error formatting disk + Error formatting partition + Error locking encrypted device + Error mounting filesystem + Error opening device + Error opening file for reading + Error opening file for writing + Error reading from offset % + Error refreshing SMART data + Error removing /etc/crypttab entry + Error removing old /etc/fstab entry + Error retrieving configuration data + Error setting label + Error setting partition flags + Error setting partition name + Error setting partition type + Error starting SMART self-test + Error starting swap + Error stopping swap + Error unlocking encrypted device + Error unmounting filesystem + Error updating /etc/crypttab entry + Error updating /etc/crypttab + Error updating /etc/fstab entry + Error writing to backup image + Every time data is collected span size=\small\(Online)/span + Extended partition + Failure is a sign the disk exceeded its intended design life period (Old-Age) + Failure is a sign the disk exceeded its intended design life period span size=\small\(Old-Age)/span + Failure is a sign the disk will fail within 24 hours (Pre-Fail) + Failure is a sign the disk will fail within 24 hours span size=\small\(Pre-Fail)/span + Fair + Filesystem Root + For logical partitions + GPT + If checked, the loop device will be read-only. This is useful if you don't want the underlying file to be modified + LUKS + Ext4 + Less than a minute + MBR / DOS + Matches any device with the given label + Matches partition %d of any device connected at the given port or address + Matches partition %d of the device with the given vital product data + Matches the device with the given UUID + Matches the given device + Matches the whole disk of any device connected at the given port or address + Matches the whole disk of the device with the given vital product data + No Media + No partitioning + No + OK + Only during off-line activities span size=\small\(Not Online)/span + Only the passphrase referenced by the i/etc/crypttab/i file will be changed. To change the on-disk passphrase, use iChange Passphrase.../i + Other Devices + SELF-TEST FAILED + SMART is not enabled + SMART is not supported + Select Disk Image to Attach + Self-test in progress — %d%% remaining +
Re: How to mark Docbook sentences as not translatable
Hi Pierre, Am 17.01.2012 20:25, schrieb Pierre Wieser: Hi all, Well, all is in the subject :) The user's manual of NACT application is written with Docbook. Translators make their best efforts to translate the manual efficiently, but the need has arisen to mark some phrases as not translatable. How should I do this ? Some Google search only directed me to ITS [1], but I am not sure if this extension is managed by Gnome translation toolchain ? Yes, it is managed by the Gnome toolchain, but for the time being it is not widely used yet, only in some Mallard-based docs. Have a look in [1] to get an impression how it is implemented. Cheers, Mario [1] http://git.gnome.org/browse/gnome-user-docs/tree/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Help with integrating Danish translation Rhythmbox (deadline tomorrow)
Am 15.01.2012 00:09, schrieb Joe Dalton: Hi Byrial has made the Danish translation and it has been proofread. We are not certain what Kenneth is reachable in time for this one. So we are kindly asking for some help with integrating this file. thanks in advance Joe Done. commit f0ae3bf99de1c002255ac582f95d171841a77db9 Author: Byrial Ole Jensen byr...@vip.cybercity.dk Date: Sun Jan 15 00:26:51 2012 +0100 [l10n] Updated Danish translation Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gnash release planned - urgent need for L10n help
I'll have a look at the German translation next days. Best regards, Mario 31.12.2011 07:51 schrieb am Chris Leonard cjlhomeaddr...@gmail.com: Dear Gnome localizers. Rob Savoye is planning a new release of Gnash in mid-January. Gnash is the GNU SWF movie player, which can be run standalone on the desktop or an embedded device, as well as as a plugin for several browsers. http://www.gnu.org/software/gnash/ http://www.gnashdev.org/ Many strings have recently been added to the Gnash project and so I am making an urgent request for assistance to the Gnome localizers for help with this important sister GNU project effort. The goal is to achieve a reasonable level of L10n coverage, both in number of languages and in the percent completion of each language. Gnash has historically used a download the POT, complete it and post it to the mailing list L10n workflow. As you might expect, this results in relatively poor L10n coverage. At present, the Gnash repository /po directory has the following submissions (only 9 languages, none of them complete). http://git.savannah.gnu.org/cgit/gnash.git/tree/po Czech 79% Danish 83% English (UK)83% Finnish 7% French 17% German 7% Italian 3% Japanese 3% Spanish 83% This is a sad state of affairs for an important free software project used around the world. The Sugar Labs / OLPC / eToys localization community has been collaborating with the Gnash community by offering hosting for the Gnash PO files on our Pootle server and contributing to Gnash localization in appreciation of their work to provide a free / libre alternative to proprietary SWF / Flash players. gnash.po files hosted here: http://translate.sugarlabs.org/projects/upstream_POT/ The Gnash PO file is currently available for translation into these 90 languages. The Gnash PO file can be made available on Pootle in other languages upon request. Acholi, Afrikaans, Akan (Twi:Asante), Albanian, Amharic, Arabic, Armenian, Asturian, Aymara (Aru), Bamanankan, Basque, Belarusian, Belarusian-latin, Bengali, Breton, Bulgarian, Catalan, Chiga, Chinese (China), Chinese (Hong Kong), Chinese (Taiwan), Croatian, Czech, Danish, Dutch, English (United Kingdom), Esperanto, Estonian, Finnish, French, Fulah, Galician, Ganda, German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Irish, Italian, Japanese, Kazakh, Khmer, Korean, Kurdish, Latvian, Lithuanian, Lojban, Macedonian, Malagasy, Malay, Mandinka, Marathi, Nahuatl languages, Nepali, Northern Sotho, Norwegian Bokmal, Norwegian Nynorsk, Pashto, Polish, Portuguese, Portuguese (Brazil), Quechua (Ayacucho-Chanka), Quechua (Cusco-Collao), Romanian, Russian, Sardinian, Serbian, Serbian-latin, Sinhala, Slovak, Slovenian, Songhai languages, Spanish, Swahili, Swedish, Swiss German, Tamil, Thai, Turkish, Tzotzil, Ukrainian, Urdu, Vietnamese, Welsh, Wolof, Yiddish, Zulu If you truly care about making free / libre software available in your native language, please consider contributing some time and effort to working on the Gnash L10n over the next few weeks. You have an opportunity to have a huge impact on the user experience of free software users and creating a viable alternative to using a proprietary SWF player. You should be able to download the gnash.po file for your language and work with it off-line in your favorite PO editor or you can register on our Pootle server and localize it on-line. If you choose to work off-line, please send your PO files to me and I will make sure that they get uploaded to our Pootle server. I will work with Rob Savoye (Gnash developer and release manager) to make sure that your contributions are included in the upcoming release. As the PO file for Gnash is quite large, off-line work may be fastest. I will try to see if it is possible to create something like a reduced PO file for Gnash that focuses on the most prominent UI strings, but in the meantime, there are many strings that need to be localized and this is a wonderful chance to make a big difference with your localization skills to start off the New Year (Gregorian). Please spread this message to any distro L10n communities that package Gnash. It would be awesome if we could turn the first few weeks of this New Year into a globally distributed translation marathon on behalf of Gnash. Thank you for your attention to this request. Time is of the essence to meet the new release date goal. Warmest Regards and a Happy and Healthy New Year to All. cjl Sugar Labs Translation Team Coordinator ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Dia 0.97.2 released
Am 18.12.2011 20:56, schrieb Hans Breuer: At 27.05.2009 09:34, Claude Paroz wrote: Le dimanche 24 mai 2009 12:42 +0200, Hans Breuer a Ă©crit : [...] Future dia-0.97.x releases may be made off that branch, while development towards dia-0.98 proceeds on master. Branch added on http://l10n.gnome.org/module/dia/ Please don't forget to remind us when translators have to work on master again. Thanks for all the translation updates just released with Dia 0.97.2. The dia-0-97 branch will most probably not have further releases [1] So future translation work should focus on dia master. OK, I've changed the view in the Damned Lies accordingly. The master branch is now an official part of the Office applications release set. Thanks for your information. Once you fork a branch for new releases, please let us know again. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translations commit request
Am 17.12.2011 19:51, schrieb Baurzhan Muftakhidinov: Hello! Could someone please commit the updated translations for Kazakh language Direct links are below http://l10n.gnome.org/vertimus/gtk+/master/po/kk http://l10n.gnome.org/vertimus/evince/master/po/kk http://l10n.gnome.org/vertimus/file-roller/master/po/kk Done. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Please add libcryptui to D-L
Hi, as far as i can see, the libcryptui library is a direct dependency of Seahorse. It should be added to the D-L pages, as part of the External dependencies release set. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Branch for libgda added to Damned Lies
Hi all, I've just added the LIBGDA_4.2 branch to the Damned Lies pages [1], due to recent changes in this branch which affect translations. The new branch hasn't been assigned to a release set yet, because I don't know if there will come more releases from. Best Regards, Mario [1] http://l10n.gnome.org/module/libgda/#LIBGDA_4.2 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Additonal branch for GNOME commander
Hi all, I've just added the branch gcmd-1-2-8 of gnome-commander to the extra apps stable release set. Seems to be that more releases will come from this branch (latest was on October 4th). In my mind it is worth to keep track of any changes. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'hamster-applet.master'
Am Sonntag, den 23.10.2011, 19:47 + schrieb GNOME Status Pages: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'hamster-applet.master': + The overview window of hamster time tracker + Time Tracking Overview Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. Your recent commits break the string freeze for GNOME 3.2. Please request a string freeze break (if there are good reasons for) or branch for GNOME 3.2 at an earlier point. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Gbrainy stable branch
Hi, recently a release set »Extra GNOME apps (stable branches)« has been added to the D-L view. But there remains still one module which belongs there to: Gbrainy has a stable branch, simply called »stable«. Please move it to the appropriate release set. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gthumb branched for version 2.14
Am 15.10.2011 16:33, schrieb Paolo Bacchilega: Hi, the gthumb module has a new branch called gthumb-2-14 which will be used for the upcoming 2.14.0 version and the future minor version releases, the master branch will be used to develop the next major release. Does this mean the 2.12 branch is deprecated? Then it should be removed from the Damned Lies view. By the way, are you planning a release from the new branch next time? Don't forget to announce a string freeze before, please. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome.org website translation
Am 11.10.2011 21:35, schrieb Pavol Šimo: Still no answer to the original question... Anyone? The temporary GNOME 3 website was based on pure HTML, that's why it could be parsed easily by html2po (from the Translate Toolkit) to get a translation template. As far as I know, our website gnome.org is based on PHP scripts. Some different workflow and tools are needed here to make it translatable. The Translate Toolkit provides a similar tool named php2po [1]. I don't know whether any changes in the PHP code are needed to make it work. Anyway, it would be fine to be able to translate it. Best Regards, Mario [1] http://translate.sourceforge.net/wiki/toolkit/php2po ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New release set
Am 26.09.2011 10:34, schrieb Andika Triwidada: On Mon, Sep 26, 2011 at 1:35 PM, Claude Paroz cla...@2xlibre.net mailto:cla...@2xlibre.net wrote: Hi all, I eventually created the stable GNOME Extra Applications release set we discussed some time ago: http://l10n.gnome.org/releases/gnome-extras-stable/ Thanks to help us keeping it up-to-date. I didn't recall which discussion, care to remind me? Anyway, will this change translation priorities of those apps to be higher than the rest of gnome-extras? Yes, of course. If a stable branch exists and is actively maintained in Git, we may expect that bugfix releases will come from that branch again. That's why they should have a higher priority. Until now we had the master branches of some of the appropriate modules in no release set. As a consequence, other release sets should also get a similar subsidiary, such as the office stuff and Gimp. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: pybliographer 1.2.15 will be released soon
Am 22.09.2011 22:02, schrieb Zoltan Kota: Hi, I plan to push a new release of pybliographer next week. Please, check your translations! Thanks! Zoltan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n There's still a problem with displaying the help. I've just installed the current Git content to /usr/local. When I try to open the manual from the menu bar, I get the following error: Can't display documentation: Unable to find help paths /usr/local/share/gnome/help/pybliographer or /usr/share/gnome/help/pybliographer. Please check your installation The appropriate files have been installed in /usr/local/share/gnome/help/pybliographer/C/ anyway. If I run yelp . in this folder, no problem, Yelp shows the help as expected. This issue should be solved before a new Pybliographer version will be published. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Requesting string freeze break for gnome-keyring
Am 09.09.2011 21:20, schrieb Stef Walter: I'd like to remove the word 'a' here: https://bugzilla.gnome.org/show_bug.cgi?id=658668 In order to fix a typo, it doesn't really indicate a freeze break. Assuming that translators have translated it correctly, it's just a thing of remove the fuzzy tag and commit the new file. However, I'm not a member of the i18n team, that's why just my 2 cents. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Release of gnome-schedule 2.1.4
Hi Gaute, just read about the new release of GNOME Schedule 2.1.4. I'm the current German translator of gnome-schedule. Unfortunately, there were some recent changes in Git which affect translations. You have added some files to POTFILES.in and rolled a new release immediately. This is a *bad* idea. Before, more than ten translations were complete, and now, no one of them anymore. Please give translators some time to get their work complete by announcing a string freeze. One week or ten days should be sufficient here. Remember, it's not for an impressive translated string count in the status pages. It's for the convenience of our users. Thanks in advance Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Boot-Repair
Am 05.08.2011 11:07, schrieb yannubu...@gmail.com: Dear all, Boot-Repair v3 is now in Feature freeze, so this is the good moment to translate it: https://translations.launchpad.net/boot-repair/trunk (only 77 strings ! ) Done for German by Christian Kirbach and me. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Is it possible to copy en-GB translations to en-AU to make the starting point for en-AU easier?
Hi Michael, Am 29.07.2011 20:34, schrieb Michael .: Good morning everyone. I was wondering if it is possible to directly copy the en-GB translations over to en-AU (because en-AU is much closer to en-GB than it is to en-US or any other en-dialect). This would make the starting point for en-AU easier as after this only small changes would need to be made. I have tried to contact Bastien from en-GB (via his personal email address listed on his website), about the python script, a few times but as yet have had no response from him so I am thinking this is a viable alternative method to accelerating the en-AU translation. Yes, of course. Just copy en_GB.po to en_AU.po, add your name to the file header and review the file. That's it. But keep in mind that any future changes to the British English translations have to be adapted to the Australian ones, too. Would be useful to figure out a way which automatizes that in some way. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: LaTeXila: some questions
Am 16.07.2011 15:33, schrieb Sébastien Wilmet: OK. itstool seems very interesting. I'll try to use it with CMake. And if I succeed, I suppose it will be well integrated with Damned Lies (for the Mallard documentation, and for the other XML file). Do you mean man/latexila.1.xml? Well, it could be translated with itstool/Damned Lies, actually. But as far as I know, we don't have any translatable or even translated manpages in GNOME. However, it is a good idea to provide a DocBook file which will be converted later to the man format. The idea is worth to be adopted by other man page authors, though. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: LaTeXila: some questions
Am 16.07.2011 18:39, schrieb Sébastien Wilmet: [...] No, sorry, I should have said that I mean data/build_tools/build_tools-en.xml. Creating a translation template with itstool works, I get a template with 46 translatable strings. If possible in some way, it could be provided by Damned Lies. For the manpage, it is not important to have translations. If it works, you don't have to think about its importance. Let translators decide whether they want to work on it. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: LaTeXila: some questions
Am 16.07.2011 18:56, schrieb Mario Blättermann: [...] Creating a translation template with itstool works, I get a template with 46 translatable strings. If possible in some way, it could be provided by Damned Lies. But keep in mind, you have to create the translated xml file(s) at build time, as for the Mallard docs, too. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Recent changes in Glom branches
Hi all, recently there were some changes in the Glom branches 1.16 and 1.18 which affect translations. These branches are still used for releases, but are not tracked in the D-L pages. I propose to let them appear at least in the module overview [1]. [1] http://l10n.gnome.org/module/glom/ Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Please add the frogr manual to D-L
Am 30.05.2011 10:30, schrieb Mario Sanchez Prada: Hi! On Sun, 2011-05-29 at 20:22 +0200, Claude Paroz wrote: Le dimanche 29 mai 2011 à 18:10 +0200, Łukasz Jernaś a écrit : 2011/5/29 Mario Blättermann mari...@freenet.de: Hello, the frogr module [1] has a Mallard based manual. It isn't complete yet, but already worth translating (currently 56 strings, including 4 pictures). Please would somebody add it to the D-L view? Hi Mario! If you add the help files to the build system they should get included on D-L as far as I remember, the attached patch should help. Not always, it depends on how the initial setup of the module has been done in D-L. I just added the missing bit. However you're right in that the build system is currently broken for the help part of frogr. I wonder if it wouldn't be better to use the new itstool based build system, as Shaun has recently done with gnome-user-docs [1]. [1] http://git.gnome.org/browse/gnome-user-docs/commit/?id=c12275f8 Claude The addition of those new files to frogr is still work in progress, in the way that we just added the .page files (and some pictures) to the source tree and we still lack some needed changes to integrate them into the build process for the project, as you have noticed. The plan so far was that Pierre (the contributor who filed the bug and provided the initial .page files) provided those needed changes to integrate it in the build process, which is something that he already did (see [1])... but now you mentioned this about a new build system for the documentation perhaps that patch he proposed would need more changes. Thing is that, as I have no idea about these kind of (help related) topics, I'm not sure about what would be the good next step to make so, so it would be awesome if someone with more knowledge could take a look to the bug currently tracking down these new additions to frogr, and comment on the patches that Pierre are sending there: https://bugzilla.gnome.org/show_bug.cgi?id=651337 Also, as I said Pierre in there, please feel free to commit whatever you want to frogr related to the addition of these new documentation related files. That probably would be faster (and safer) that relying on me to review and commit changes :-) (after all, I don't have the proper knowledge for that yet) Last, but not least, please accept my apologies if adding these new files without integrating them into the build+translations machinery annoyed you in some way. If that's a problem because of some reason (I don't know, perhaps it broke something in the l10n machinery), we could always withdraw those files by now, keep iterating in the bug, and apply them back once an atomic patch is ready. Due to that the *.page files are already committed, the patch won't become that big. In any case I would prefer the bleeding edge way by using itstool. The new gnome-user-docs (master) is an example. @Łukasz: Would you have a look at it? Although I've migrated some docs to the gnome-doc-utils workflow, I'm not familiar yet with yelp-tools and the appropriate utilities. Perhaps we should ask for help in the gnome-doc-list anyway (CC'ed). Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Please add the frogr manual to D-L
Hello, the frogr module [1] has a Mallard based manual. It isn't complete yet, but already worth translating (currently 56 strings, including 4 pictures). Please would somebody add it to the D-L view? Best Regards, Mario [1] http://git.gnome.org/browse/frogr/tree/help/C ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating gnome-help
Am 22.05.2011 15:56, schrieb Nguyen Thai Ngoc Duy: On Sat, May 21, 2011 at 2:39 AM, Claude Paroz cla...@2xlibre.net wrote: You can now get proper pot/po files to start translating the 3.2 version, even if the doc team is probably working hard to update it during the dev cycle. http://l10n.gnome.org/module/gnome-user-docs/ I don't know which product to report to, so I ask here instead. Comments in .page files are also put in po templates. Should they not be there (and translation teams not wasting time translating them)? It's probably xml2po, or mallard, I don't know.. The image handling is still broken and definitely on my todo list... http://library.gnome.org/users/gnome-help/nightly also does not work. Not that I push any more work on your todo list :P The problem is our good old xml2po. It cannot handle things properly, which should be actually untranslatable. Once the successor itstool [1] is established, we don't have to annoy about such stuff any longer. A Fedora package is currently under review [2]. BTW, some of the comments are just artifacts from the early state of the user manual, just stubs. For my, I have copied the contents, because it is not useful. Once these strings change to real information, we will be get informed by the D-L tracker anyway. Cheers, Mario [1] http://itstool.org/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=702989 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Problem in Vertimus view for gLabels
Hi, the gLabels module [1] has recently branched into glabels-3_0. With my co-maintainer hat on, I'm able to assign existing branches to a certain release set. Well, I did so, and assigned the new branch to extra applications and removed master. No problem so far. Translators which open the appropriate link from the overview page of their language, get the correct file presented. But the overview page displays the master branch in the first stage as usual, then the deprecated glabels_2_2 branch and as the last one the current glabels-3_0 branch. The latter is even collapsed, as known from deprecated branches in other modules. The correct sort other should be master/3_0/2_2(collapsed). Did I something wrong here? Moreover, the Branches: row shows some problems with master and glabels_2_2, but no info about where to find the affected languages in particular. Best Regards, Mario [1] http://l10n.gnome.org/module/glabels/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Problem in Vertimus view for gLabels
Am 19.05.2011 21:34, schrieb Claude Paroz: Le jeudi 19 mai 2011 à 21:17 +0200, Mario Blättermann a écrit : Hi, the gLabels module [1] has recently branched into glabels-3_0. With my co-maintainer hat on, I'm able to assign existing branches to a certain release set. Well, I did so, and assigned the new branch to extra applications and removed master. No problem so far. Translators which open the appropriate link from the overview page of their language, get the correct file presented. But the overview page displays the master branch in the first stage as usual, then the deprecated glabels_2_2 branch and as the last one the current glabels-3_0 branch. The latter is even collapsed, as known from deprecated branches in other modules. The correct sort other should be master/3_0/2_2(collapsed). Did I something wrong here? Hi Mario, The problem is related to sorting with the inconsistent naming scheme (mix of _ and -). But fortunately D-L has superpowers :-) We have a field to tweak branch ordering (weight), but it is not exposed in the public interface. This should be fixed now. Moreover, the Branches: row shows some problems with master and glabels_2_2, but no info about where to find the affected languages in particular. It is just a warning to remind you that those branches are not linked from any release. Cheers, Claude Hi Claude, thanks for your fast response. Now it looks like it has to look :-) However, Jim made the decision to name the new branch whithout thinking about it. But thanks to the »superpower«, the problem is now solved. In general, I recognize the Damned Lies as the best tracking tool and translation utility ever. It is much better than Launchpad or Transifex, although it has no web interface (don't misunderstand me, I don't need it, this is no »feature request«). Many thanks for your work. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: fantasdic doc
Am 30.04.2011 20:36, schrieb Коростіль Данило: Where may I find po files for doc, huh? I can't find anywhere. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n http://l10n.gnome.org/module/fantasdic/ The pot template, which you might use for Ukrainian (guessed by me): http://l10n.gnome.org/POT/fantasdic.master/docs/fantasdic-help.master.pot But keep in mind, there were no commits to this module for more than a year, excepting translations. It should have a low priority for you. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: fantasdic doc
Am 30.04.2011 21:13, schrieb Коростіль Данило: On 30.04.11 22:06, Mario Blättermann wrote: Am 30.04.2011 20:36, schrieb Коростіль Данило: Where may I find po files for doc, huh? I can't find anywhere. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n http://l10n.gnome.org/module/fantasdic/ The pot template, which you might use for Ukrainian (guessed by me): http://l10n.gnome.org/POT/fantasdic.master/docs/fantasdic-help.master.pot There is no doc directory inside of repository. But keep in mind, there were no commits to this module for more than a year, excepting translations. It should have a low priority for you. As you may see I need to update uploaded file there: http://l10n.gnome.org/vertimus/324/294/36 Fantasdic behaves some different from other modules. The doc folder is data/gnome/help/fantasdic. After adding the file uk/uk.po, you have to add uk to the file LINGUAS, which is actually unusual for docs. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [BillReminder] Created branch billreminder-0.4.0
Am Montag, den 03.01.2011, 11:01 -0500 schrieb Og Maciel: All, I forgot to announce that I created a new billreminder-0.4.0 branch for BillReminder and would like D-L to be updated to reflect these changes. As a member of the GTP and the registered maintainer of the Billreminder module, you should be able to do this for yourself. Check the overview page for billreminder at D-L: http://l10n.gnome.org/module/billreminder/ You should see a small symbol displaying a paper sheet with a magnifier and a pencilk at the end of the line which links to the branches. Click this symbol to open a settings page for your module. Here you can assign any Git branch to a release set. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: No link for .po file in gnome-web-photo master
Am Dienstag, den 28.12.2010, 01:44 +0100 schrieb Daniel Șerbănescu: În data de Ma, 28-12-2010 la 01:17 +0100, Andre Klapper a scris: Am Dienstag, den 28.12.2010, 00:45 +0100 schrieb Daniel Șerbănescu: Hi, when I try to dowload the .po file from : http://l10n.gnome.org/vertimus/gnome-web-photo/master/po/ro ... I get the .POT file ... And when I try the pattern like: http://l10n.gnome.org/POT/gnome-web-photo.master/gnome-web-photo.master.sv.po if I replace „sv.po” with „ro.po” at the end it says not found... Could someone please fix that. What is your exact request? That for a non-existing po file (translation) there should be an automatic redirect to the pot file? andre The issue was that when I clicked the button „download” (like in this image: http://live.gnome.org/TranslationProject/ContributeTranslations?action=AttachFiledo=gettarget=l10n-reserve.png) I got a pot file instead a .po one like it should Now it seems to work... so nevermind ... sorry for disturbing.. It also works for me, even I'm not a member of the Romanian team. Normally, if there's no translation for your language yet, Vertimus creates a fake *.po file from the current *.pot. This should work always if you are logged in to your account. If not, you get a *.pot file because Vertimus doesn't know in this case for which team member the *.po file should be created. See the line with your name and mail address in the file header. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Untranslatable strings in the gLabels manual
Hi all, there are some strings in the gLabels manual which shouldn't be translated. These strings refer to property values which are used in the template files. If a template file contains such values, it cannot be parsed by libglabels, and the appropriate label or card will not appear in the template chooser. To remove them from the *.pot file (and the *.po files, too), I tried to mark them as follows, as suggested by Shaun McCance: span its:translate=nountranslatable value/span Unfortunately, our xml2po can't handle this yet. This tool from the gnome-doc-utils package will be likely replaced by itstool [1] in the nearest future. This is a new parser which is developed close to the ITS recommendations [2]. Then I tried to omit the its to get it parseable with the current tools, but it doesn't work yet. For the time being, if you encounter a string in this manual which is enclosed in a span tag, you dont't have to translate it. Some of these tags appear also inside other strings: #: C/mancreate.page:163(title) msgid span translate=\no\Template/span Node msgstr span translate=\no\Template/span-Knoten Please leave the content embedded in these tags also untranslated. Thank you for all your work, and a Merry Christmas! Mario [1] http://gitorious.org/itstool/pages/Home [2] http://www.w3.org/TR/its/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gsettings-desktop schemas
Am Mittwoch, den 22.12.2010, 17:40 +0200 schrieb Lucian Adrian Grijincu: 2010/12/20 Mario Blättermann mari...@gnome.org: The question is now: does it make sense to make the keys translatable? If the answer is yes (for whatever reasons) it would be extremely nice to have them in a separate .po file. In my view the priority is: UI, help, gsettings, but because UI and gsettings are mixed together and because humans have an urge to finish the job, gsettings strings get translated to make the whole file 100% complete. Doesn't matter. The urge to deliver 100% is no burden for me ;) But I agree with you. Some teams like to skip the schema strings for now anyway. That's why the handful of GSettings based module maintainers could think about to split the po files as GTK already does for a long time. In GTK, there are the folders po and po-properties. The second one is for property nicks which likely appear in the terminal only. We could do it similarly. We create a folder po-gsettings and fill the file POTFILES.in with the names of the gsettings-related files. Just introduce it to the autotools stack, and we can go ahead. One hand, we have satisfied translators, other hand, the other translators which actually want to translate it may skip it until dconf-editor really works. But this procedure works only if we have the gsettings keys always in separate source files, apart from other code. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gsettings-desktop schemas
Hi all, some months ago the gsettings-desktop-schemas module was added to the Damned Lies pages. It rests in peace since, because the status view shows zero strings from the beginning. The command »intltool-update« cannot detect any translatable strings. The file POTFILES.in shows entries like the following: schemas/org.gnome.desktop.default-applications.gschema.xml I've tried to prepend a [type: gettext/xml] to each line, but it doesn't work. Even when I change descriptionWhether the on-screen keyboard is turned on./description to _descriptionWhether the on-screen keyboard is turned on./_description it doesn't work not yet. What's the matter here? Which prerequisites are needed to make it work? It's a pity that we have a module which seems to be important (otherwise Andre hadn't asked to add it) and we cannot translate it. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gsettings-desktop schemas
Am Montag, den 20.12.2010, 15:41 +0100 schrieb Andre Klapper: Am Montag, den 20.12.2010, 15:45 +0100 schrieb Mario Blättermann: Which prerequisites are needed to make it work? First question is: Why should it be translated? Andre, if I remember correctly, you was the guy who had asked for add it to the Damned Lies...? You should actually know why. Currently it only contains scheme descriptions, and I don't know of any user interface application that displays them. Of course it contents only scheme descriptions, as the module name suggests. Scheme descriptions are displayed in gconf-editor, and it is really important in my mind to have them localized, although some GTP teams want to skip them. We have this tool for rarely used and not in the UI available settings, and the localized scheme descriptions mark a difference to other configuration databases. The human-readability is the most important advantage of gconf-editor, and we should keep this by providing descriptions in the native languages of the users. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gsettings-desktop schemas
Am Montag, den 20.12.2010, 16:38 +0100 schrieb Andre Klapper: This certainly applies for gconf scheme descriptions but I have no idea if that app works with gsettings/dconf. In the current gconf-editor it doesn't work, but the dconf-editor (with is mostly part of the dconf package, at least on my system) shows this settings. There are *some* apps which have already migrated to GSettings, such as brasero, nautilus-sendto, glabels etc. Those key descriptions are displayed in dconf-editor. Am Montag, den 20.12.2010, 16:46 +0100 schrieb Luca Ferretti: Here is dconf-editor in dconf module, while currently it needs love. A lot of love. You are right. The current v0.5.1 is still missing a menu bar, an appropriate search function and some things more. Hope it becomes better for the GNOME 3 release. The question is now: does it make sense to make the keys translatable? Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Something wrong with bug-buddy doc?
Am Sonntag, den 19.12.2010, 12:35 +0100 schrieb Jorge González González: Hi all, is there anything wrong with the bug buddy documentation? http://l10n.gnome.org/vertimus/bug-buddy/master/help/es There is no really documentation. In the Git tree I found a manpage only, and a naked manpage without any other stuff (appropriate Makefile.am and OMF file) cannot be parsed by the gnome-doc-utils. As far as I know, some explanations for bug-buddy are in the Desktop User Manual. Recently, there appeared some other manuals in the Damned Lies which were also untranslatable yet. For gnome-pilot and genius I have added g-d-u support immediately, and the meld manual shouldn't be translated for the time being, after consulting the meld maintainer, because it is outdated. A new build system for meld will be implemented anyway next time, probably autotools or waf. Why appears the non-existent manual of bug-buddy in D-L? No idea... Could be that Vertimus parses the Git content regularly. But there's nothing which resembles a DocBook or Mallard hierarchy. And I remember, in the last years a similar bug-buddy manual appeared several times in D-L and disappeared again some time later from it, also with zero translatable strings. A bug in the parser routines of Vertimus? Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Something wrong with bug-buddy doc?
Am Sonntag, den 19.12.2010, 14:22 +0100 schrieb Mario Blättermann: There is no really documentation. In the Git tree I found a manpage only, and a naked manpage without any other stuff (appropriate Makefile.am and OMF file) cannot be parsed by the gnome-doc-utils. As far as I know, some explanations for bug-buddy are in the Desktop User Manual. Oops, just seen that there *was* a translatable manual for bug-buddy. Last seen in the gnome-2-24 branch. It is no more to find in master. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Gnac manual not in Damned Lies
Hi, the Gnac module has a translatable manual. I've just added gnac.omf.in to make it considerable by gnome-doc-utils. However, it's in an early state, but already more than a skeleton. Could somebody add it to the Damned Lies pages please? Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Pybliographer manual is under construction
Am Donnerstag, den 28.10.2010, 19:56 +0200 schrieb Mario Blättermann: Hi all, some weeks ago the DocBook manual of Pybliographer [1] had migrated to use gnome-doc-utils/xml2po/gettext for the translation workflow. In the meantime, some translations have arrived. Currently the manual will be migrated to Mallard. That's why you shouldn't be surprised that the po files contain just a handful strings. Actually, the *.page files are not recognized in the build process, but they are already detected by Vertimus for updating the status pages. I think I need some weeks for the migration. Well, a big part of the existing material will be reused, but for the time being, you shouldn't waste your time with doc translations. The Mallardization is finished now. The doc status has pushed to final. There won't be any significant changes before the next version will be released. However, I don't announce a string freeze for the time being, but if you want, you can translate it now. Thanks for all your work (already done and in the future)! Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Please add Postr to the D-L pages
Hi, just seen that the postr module in our Git includes isn't displayed anywhere in the Damned Lies. The module includes a gettext stack for the GUI translation and a Mallard-based manual. Would anobody add this and assign it to the Extra apps release set please? Many thanks. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
RE: accounts-dialog
I notice that new translations for the accounts-dialog module are still coming in. The accounts-dialog has been merged into gnome-control-center, as user-accounts panel. There will be no more releases of the standalone accounts-dialog, so please don't waste effort on translating it. Then it should be removed from the Damned Lies pages completely (or probably moved to the Obsolete apps page). Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xml errors in documentation
Am Mittwoch, den 20.10.2010, 00:36 +0200 schrieb Ask Hjorth Larsen: This is a breakdown of every xml error in every translated documentation string in GNOME for those languages that have reasonable ( around 10%) coverage of the documentation. More precisely, every message where the English string is valid xml, but the translation is not. You may want to fix them as this probably means the messages are not displayed correctly in the help documents. … ./de/summary.txt:Total errors 14 These errors are fixed now for all the mentioned modules in German. Thanks for the hint. Best Regards, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Pybliographer manual is under construction
Hi all, some weeks ago the DocBook manual of Pybliographer [1] had migrated to use gnome-doc-utils/xml2po/gettext for the translation workflow. In the meantime, some translations have arrived. Currently the manual will be migrated to Mallard. That's why you shouldn't be surprised that the po files contain just a handful strings. Actually, the *.page files are not recognized in the build process, but they are already detected by Vertimus for updating the status pages. I think I need some weeks for the migration. Well, a big part of the existing material will be reused, but for the time being, you shouldn't waste your time with doc translations. Cheers, Mario [1] http://l10n.gnome.org/module/pybliographer/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glabels has moved to Office Applications in D-L
Hi all, just for your information and to avoid long searches: In consultation with the maintainer Jim Evins I have moved the Glabels module from the Extra GNOME apps to Office productivity apps. Well, the GNOME Office is a loose collection of office apps, not comparable with the highly integrated OpenOffice. But Glabels aims to be an application for office use, that's why I did so. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Banshee master string frozen until Sept 29/1.8.0
Am Dienstag, den 28.09.2010, 09:10 +0200 schrieb Olav Vitters: Will it it still cause problems for translators themselves when translating the module? No, it doesn't seem to affect the Vertimus workflow. I've committed my translation some hours ago, and Vertimus has merged it, and all the new strings from Hyena are still present. Cheers, Mario Exklusiv: Neue E-Mail-Adresse @iPhone.de jetzt verfügbar! Sichern Sie sich jetzt ihre persönliche http://www.iphone.de/iphonemail/index.html?pid=10111947021 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Please Help to commit Uyghur translations(6 Files)
Hi Gheyret, Well, I can do this for you, assuming these translations are really ready for commit. In fact, you are a committer for your team, regardless you have an own git account or not. But you should mark the files as Ready for commit before. Cheers, Mario Exklusiv: Neue E-Mail-Adresse @iPhone.de jetzt verfügbar! Sichern Sie sich jetzt ihre persönliche http://www.iphone.de/iphonemail/index.html?pid=10111947021 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Sending to master branch
Am Samstag, den 18.09.2010, 20:20 +0200 schrieb Matej Urbančič: Hello, I'd like to ask again, in case something changed ... Comparing modul on Gnome http://l10n.gnome.org/vertimus/gst-plugins-good/master/po/sl and on translation project http://translationproject.org/domain/gst-plugins-good.html for Slovenian language it shows, that TP shows current version 0.10.23.2 as fully translated, while Gnome shows current master as missing 7 translations. SO, how do I send to master branch version of translation to TP? Nothing to do, really! The status page from TP shows the translation percentage of the *latest release* which means the status of the latest po files sent by the developers to the TP robot, while our status page shows the current state from the Git/SVN, respectively. Vertimus merges the current po files with the latest changes in Git/SVN, the TP robot doesn't do so. You shouldn't compare this. Perhaps it should be a good idea to use the percentages from the TP status pages instead of the current merged files from Git. So we could avoid such misunderstandings. Does anybody have an idea how to implement this in Vertimus? Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n