Re: Totem branched for 2.28
Thanks, this clarified many points. Andre Klapper wrote: > Hi, > > Am Mittwoch, den 30.09.2009, 09:39 + schrieb Sveinn í Felli: >> Actually there's a bigger problem with the icelandic >> translations; almost all recent translations are not merged >> into the actual/updated po file, they just lie in DL like >> sitting ducks along with the old po. > > That's because somebody has to commit them to GIT. According to > http://l10n.gnome.org/teams/is it looks like you have nobody with GIT > access... Hmm?? Well, the coordinator should get one, isn't it? > >> I've contacted the is-coordinator and filed a bug > > URL, please? https://bugzilla.gnome.org/show_bug.cgi?id=594667 > >> but no-one >> seems to be able to push those translations. > >> If there is a howto describing handling of translations in >> DamnedLies (for translators), I'd appreciate a link. > > There probably is something in > http://live.gnome.org/TranslationProject/ . Read, but not so clearly. > > andre So, to push my translations into git, should I ask someone to do it by sending a message to a) this list b) directly to a person with git access c) file a bug ? Thanks for your attention Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME Color Manager
Hi, Tirumurti Vasudevan wrote: > On Mon, Nov 2, 2009 at 4:34 PM, Tirumurti Vasudevan > wrote: > pl let me know what you are trying to say here. > > //#: ../src/gcm-calibrate.c:252 > msgid "Please attach the hardware device to the center of the screen > on the grey square."// > You must be referring to a "profiling device" or a "spider"? Does the term have to be so generic? Best, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Sending to master branch
Hi, I think they use 'HEAD' insted of 'master', at least once I've sent a file to a HEAD-branch. And there should be a dot. So your file should be renamed 'gst-plugins-bad.HEAD.sl.po' My 2 centimes. Sveinn í Felli Þann fim 8.júl 2010 10:46, skrifaði Matej Urban: The actual error message is: Hi! I am the service robot at the Translation Project, and was awakened by one of your submissions. ***> As file name you supplied 'gst-plugins-bad-master.sl.po'. In this I cannot find the domain name, the version number, nor the team code. The file name should look like 'DOMAINNAME- VERSIONNUMBER.TEAMCODE.po' (all in lowercase). Some error reported above (marked with "***>") prevents me from accepting your PO file. Sorry! But do not hesitate to resubmit your PO file, once you think the problem has been fixed. As a robot I am incredibly patient at these things! The Translation Project robot, in the name of your kind translation coordinator. Since there is no numbers, the tprobot does not know that this is master branch. M! ___ 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: GNOME Moduleset Reorganization vs. L10N
oordinators can prioritize certain translations, but then such matters can be discussed on mailinglists. Web-translation can be enabled or not for individual files. LP is getting better, but it's a pain searching for a particular phrase or downloading all po/pots for a certain language. Not mature. Don't forget the KDE-way; great stats, not tremendously difficult to set up svn+ssh. But then, KDE is probably going the git-way soon. Just some thoughts, Sveinn í Felli I guess it is prefered to respond to the thread on desktop-devel-list mailing list and CC gnome-i18n@ to not have two separate threads on the same topic and to create better understanding/awareness on both sides (developers and translators) for issues. Done. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating schema files
Þann lau 30.okt 2010 15:54, skrifaði Gil Forcada: El ds 30 de 10 de 2010 a les 11:30 +0200, en/na Johannes Schmid va escriure: --- Hopefully with Damned-Lies with git this translator will have more time to do their job instead of opening terminals :) +1 --- I could also go further and separate the platform as a second-step translation, that way a translator path for reaching the glorious 100% should be: - translate the ui - translate the errors - translate the schemas - translate the platform +1 Prioritizing translation work is a must. Being able to catch new/changed UI-strings as soon as possible is a must. Most places I'm translating (Gnome, KDE, Openoffice/LibO, TP, Launchpad, etc.) there have been discussions about categorisation of strings, some different roads have been proposed, but I think the above proposition by Gil is quite realistic. It's not about egos, it's about splitting the work into small chunks so that translators can start working on the stuff that 99% of the users will see and then, if they have time (note that only 50 teams out of 120 reach the 80% mark) work on adding an extended experience with schemas and errors translated. It's not about egos, it may not even be about Gnome per se; for many translation teams it's about user experience and to have a fully translated Desktop Environment (which may depend on more strings than come from the DE of choice). And the users I'm mostly concerned about are *not* those who are likely to see much of the 'deeper' error/config messages. Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
GIMP: localisation of brushes, textures, patterns and gradients
Hi, I'm having trouble finding information on how to localise names of brushes, textures, patterns and gradients in GIMP, and palettes as well. I do see the files under /usr/share/gimp/2.0/ and surely could translate them with a text editor. But are these not translatable via gettext ? Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Committer role?
Hi, Just wondering; a committer status in Damned Lies gives what kind of permissions; to submit files into DL-queue or what else ? My status in DL is "Member of Icelandic team (Committer)" but for the Icelandic team (is) the "Team membership" section is as follows: Committers No committers Reviewers No reviewers Translators No translators Is git access totally necessary to submit files from the DL-queue (to git repo) ? Last I heard the git-access for our (very much inactive) coordinator was not working properly (I'm not complaining, just researching). I did not find any good documentation explaining the commitment to git process, apart the https://wiki.gnome.org/TranslationProject/GitHowTo which is a bit into the technical details ;-) Hope someone can explain. Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Committer role?
Hi, Just wondering; a committer status in Damned Lies gives what kind of permissions; to submit files into DL-queue or what else ? My status in DL is "Member of Icelandic team (Committer)" but for the Icelandic team (is) the "Team membership" section is as follows: Committers No committers Reviewers No reviewers Translators No translators Is git access totally necessary to submit files from the DL-queue (to git repo) ? Last I heard the git-access for our (very much inactive) coordinator was not working properly (I'm not complaining, just researching). I did not find any good documentation explaining the commitment to git process, apart the https://wiki.gnome.org/TranslationProject/GitHowTo which is a bit into the technical details ;-) Hope someone can explain. Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committer role?
Got a reply off-list: Þann fim 8.jan 2015 21:14, skrifaði Rafael Ferreira: A contributor with role Commiter or Coordinator doesn't need to have git access to submit files in D-L web interface. Before this feature exists in D-L, Git access was required for these roles to submit translations. Actually, the role in D-L wouldn't matter if you had Git access for other reasons. So, I read between the lines that there should be a "commit-to-repo" feature in D-L; I've never seen that despite having a Committer status. Where can I see it in the D-L interface? Is it possible that there's a bug in the setup for the team; since I'm a committer and in the Icelandic team but the Icelandic team does not seem to have any committers; could there be mangling of language codes ([is_IS] for me vs. [is] for the team) or some other setup error ? If for some reason you need/want to submit translations to GNOME repositories via command line, instead of D-L web interface, then Git access is required and the best documentation for that very same you provided. Maybe you want to google around from some video about Git concepts. I'm used to offline translations via CVS, SVN, TX-client and such; Git is not an alien concept. Nowadays, Git is still required if you want to perform 'git cherry-pick' from one branch to another, which is not a big deal, IMHO. Cheers, Rafael Ferreira Best regards, Sveinn í Felli 2015-01-08 10:38 GMT-02:00 Sveinn í Felli : Hi, Just wondering; a committer status in Damned Lies gives what kind of permissions; to submit files into DL-queue or what else ? My status in DL is "Member of Icelandic team (Committer)" but for the Icelandic team (is) the "Team membership" section is as follows: Committers No committers Reviewers No reviewers Translators No translators Is git access totally necessary to submit files from the DL-queue (to git repo) ? Last I heard the git-access for our (very much inactive) coordinator was not working properly (I'm not complaining, just researching). I did not find any good documentation explaining the commitment to git process, apart the https://wiki.gnome.org/TranslationProject/GitHowTo which is a bit into the technical details ;-) Hope someone can explain. Best regards, Sveinn í Felli ___ 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: Committer role?
Þann fös 9.jan 2015 13:16, skrifaði Rafael Ferreira: >So, I read between the lines that there should be a "commit-to-repo" feature >in D-L; I've never seen that despite having a Committer status. >Where can I see it in the D-L interface? There was not much change in D-L web interface about this feature, except that if you are a Commiter or Coordinator, the action dropdown menu will reveal the action "Send to repository" right after "To Commit" or "Proofread". I only see the following options on a page for a file: (e.g. at https://l10n.gnome.org/vertimus/gimp/gimp-2-8/po/is or https://l10n.gnome.org/vertimus/gimp/gimp-2-8/po/is/level1/) Action: Reserve for translation Write a comment Inform of submission Archive the actions Comment: [Browse] Upload a .po, .gz, .bz2 or .png file [Submit] None of the actions you mentioned are available. Curious? Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committer role?
Þann lau 10.jan 2015 11:43, skrifaði Baurzhan Muftakhidinov: On Sat, Jan 10, 2015 at 4:28 PM, Sveinn í Felli wrote: Þann fös 9.jan 2015 13:16, skrifaði Rafael Ferreira: So, I read between the lines that there should be a "commit-to-repo" feature in D-L; I've never seen that despite having a Committer status. Where can I see it in the D-L interface? There was not much change in D-L web interface about this feature, except that if you are a Commiter or Coordinator, the action dropdown menu will reveal the action "Send to repository" right after "To Commit" or "Proofread". I only see the following options on a page for a file: (e.g. at https://l10n.gnome.org/vertimus/gimp/gimp-2-8/po/is or https://l10n.gnome.org/vertimus/gimp/gimp-2-8/po/is/level1/) Action: Reserve for translation Write a comment Inform of submission Archive the actions Comment: [Browse] Upload a .po, .gz, .bz2 or .png file [Submit] None of the actions you mentioned are available. Curious? Best regards, Sveinn í Felli Hi, First you need to reserve it for translation, then you will see the option to upload PO file, then you can mark it as Ready for submission, and then only you can send it to repository. So actually there are 4 steps. Great, thanks a lot Baurzhan, just what I was looking for ;-) It was the first step I was missing. Now it works as intended. Thanks again, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committer role?
Þann mið 14.jan 2015 15:25, skrifaði Piotr Drąg: 2015-01-10 15:12 GMT+01:00 Sveinn í Felli : Great, thanks a lot Baurzhan, just what I was looking for ;-) It was the first step I was missing. Now it works as intended. Hi, I noticed you've committed updated translations to stable gnome-3-14 branches on several modules. That's great, but you should also remember to commit to master, currently at <https://l10n.gnome.org/languages/is/gnome-3-16/ui/>, so that all future releases will have the lastest translations as well. I think I cherry-picked and pushed to master all the translations that you did so far, but please keep that in mind from now on. Yes, it was intentional to submit to gnome-3-14 first, was testing the resulting MO files on my system (which is more or less gnome-3-14 based). Maybe I'll try to setup a summit workflow for GNOME on my machine. Thanks a lot for the upward pushing. Sveinn ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Typo in gimp.master.po ?
Circa line 2800: #: ../app/actions/filters-actions.c:178 #, fuzzy #| msgid "_Fade..." msgctxt "filters-action" msgid "_En_grave..." msgstr "" "_En_grave..." contains two underscores ??? Regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New DL option for committers
Þann þri 20.okt 2015 05:56, skrifaði Michael (C0bb3r): Hi Rafael. Thanks for your reply. Ok, I'm looking at the Australian English page for Bibijen Gnome 3.18 (which I translated a couple of weeks ago) now and I do not see any options to Review. In the New Action box the dropdown for Action only has the options Reserve for Translation, Write a comment, Inform of Submission, and Archive the Actions. So my next question is how do I review my files when there is no option presented to me to do it? Start by choosing "Reserve for Translation" and click "Submit". Then you will be offered "Upload the new translation", choose your file and click "Submit". Then you're presented to several options; guess "Ready for submission" is the one you'll be interested in. --> "Submit". At last; again several options, probably the "Submit to repository" will interest you --> "Submit". Took me 4 years to figure this out ;-) (even had to ask on this list) Once you have seen the process in action, you understand that D-L is not really a translation tool but a web-interface for managing translation files for a huge organization - with some advantages, and with some weak spots. Best regards, Sveinn í Felli On 20/10/15 12:32, Rafael Fontenelle wrote: 2015-10-19 22:17 GMT-02:00 Michael (C0bb3r) mailto:transl...@cobber-linux.org>>: I'd just like to reinforce some of what Arash has said. I find Gnome's translation tool difficult and even though I am the coordinator of en_AU I have never been able to commit anything I have done. This leaves people frustrated and they go onto other projects. As a coordinator, your credentials should have all the permissions needed. Probably you just didn't figure out how to do it. Basically, you're looking for the "Submit to repository" option, which will send the PO file to the repositories and will archive the translation status. However, you will only be able to "Submit to repository" when translation's status is "Proofread" (when a review was sent) or "To Commit" (when it is all ok, therefore ready to submit). I hope it helped. Rafael Fontenelle ___ 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: New DL option for committers
Þann fim 22.okt 2015 03:15, skrifaði Michael (C0bb3r): Sveinn again thank you, you are a legend.I have successfully committed my first translation to the system and I wouldn't have done it if it wasn't for your assistance. I didn't understand that D-L needed to see each individual job done even though I review each translation as I do it I should have asked years ago. Well, this is sort-of how FOSS works; Rafael Ferreira and Baurzhan Muftakhidinov pointed me to this workflow, now I fed it to you, and someday you'll surely give hints to somebody else. OTOH, the submitting process in D-L is clearly quite non-intuitive, despite being rather logical once you have gone through these steps first time. Don't know exactly how it could be explained better, or being made more visible. Best regards, Sveinn í Felli P.S. I even used the new option to sync it with the Master branch. On 20/10/15 18:48, gnome-i18n-requ...@gnome.org wrote: New DL option for committers Start by choosing "Reserve for Translation" and click "Submit". Then you will be offered "Upload the new translation", choose your file and click "Submit". Then you're presented to several options; guess "Ready for submission" is the one you'll be interested in. --> "Submit". At last; again several options, probably the "Submit to repository" will interest you --> "Submit". Took me 4 years to figure this out (even had to ask on this list) Once you have seen the process in action, you understand that D-L is not really a translation tool but a web-interface for managing translation files for a huge organization - with some advantages, and with some weak spots. Best regards, Sveinn ? Felli ___ 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: New DL option for committers
Þann fim 22.okt 2015 14:32, skrifaði Rafael Fontenelle: https://l10n.gnome.org/help/vertimus_workflow/ The above workflow image might help. Actually no; I did see that one, and I found also some bits and pieces on the web - but nothing sufficiently clear for my poor little brain to figure this out by myself ;-( This flowchart reminded me on how easy it is to get confused while speaking to plumbers about drainage and such; they think about the systems from sea-level and up, while their customers think down from the sink... ;-) Sveinn ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translations in Zanata
Þann fim 4.feb 2016 14:36, skrifaði Baurzhan Muftakhidinov: On Thu, Feb 4, 2016 at 7:24 PM, Lubomir Rintel wrote: Hi, the NetworkManager is now translated via Zanata [1]. This means the translators no longer need to file Bugzilla tickets with translations. Details here [2]. The bits that are in GNOME infrastructure (applet and the VPN plugins) stay there; only the NetworkManager core was added to Zanata. We're not sure if it makes sense to move to Zanata; input from translators would be very appreciated. [1] https://fedora.zanata.org/project/view/NetworkManager [2] https://wiki.gnome.org/Projects/NetworkManager/L10N Thank you, Lubo ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n Hi, I'd better have translations of nm-applet as it is - in GNOME infrastructure. +1 Regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: About translating GIMP website (gimp.org)
Þann mán 30.maí 2016 09:03, skrifaði Mario Blättermann: 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. Please consider that there's a lot of very small language-teams, so the first-run at a translated website would probably be the opening page/intro + the download page (+ any navigation elements). Extremely small teams may even judge that sufficient. Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Typo in gnome-documents.gnome
Hi, Found this curious string in gnome-documents.gnome-3-26.is.po (and in 3-24 too): #: data/ui/help-overlay.ui:106 msgctxt "shortcut window" msgid "Rotate anti-clockwise" msgstr "" Well, "anti-clockwise" is not so common English, while "counter-clockwise" certainly is correct. Unless somebody can demonstrate otherwise, I'd think this is an error. Guess that most of the translations must be correct, so this could be considered as a cosmetic change to do later, but of course it will continue to be a bit weird for native English speakers... Any thoughts? Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Typo in gnome-documents.gnome
Þann mán 25.sep 2017 11:39, skrifaði Piotr Drąg: 2017-09-25 10:52 GMT+02:00 Sveinn í Felli : Hi, Found this curious string in gnome-documents.gnome-3-26.is.po (and in 3-24 too): #: data/ui/help-overlay.ui:106 msgctxt "shortcut window" msgid "Rotate anti-clockwise" msgstr "" Well, "anti-clockwise" is not so common English, while "counter-clockwise" certainly is correct. Unless somebody can demonstrate otherwise, I'd think this is an error. Guess that most of the translations must be correct, so this could be considered as a cosmetic change to do later, but of course it will continue to be a bit weird for native English speakers... Any thoughts? Hi, From what I understand, this is actually the British form. It is a bug, as we use en_US for the source strings. You should report it against gnome-documents in Bugzilla. Best regards, Done: <https://bugzilla.gnome.org/show_bug.cgi?id=788126> Sveinn ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
DL refuses upload of Windows installer
When trying to submit gimp.po-windows-installer.master.is.po to the repository, I get this: [An error occurred during applying your action: The commit failed. The error was: “[Errno 1] b"remote: translations user cannot modify 'po-windows-installer/LINGUAS' \nTo ssh://git.gnome.org/git/gimp\n ! [remote rejected] master -> master (pre-receive hook declined)\nerror: failed to push some refs to 'ssh://git.gnome.org/git/gimp'\n"”] Any idea what's going on? Is Icelandic missing from the LINGUAS-file? best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: DL refuses upload of Windows installer
Þann fös 5.jan 2018 11:49, skrifaði Rafael Fontenelle:
2017-12-30 15:15 GMT-02:00 Piotr Drąg :
2017-12-30 17:48 GMT+01:00 Changwoo Ryu :
2017-12-30 16:12 GMT+09:00 Sveinn í Felli :
When trying to submit gimp.po-windows-installer.master.is.po to the
repository, I get this:
[An error occurred during applying your action: The commit failed. The error
was: “[Errno 1] b"remote: translations user cannot modify
'po-windows-installer/LINGUAS' \nTo ssh://git.gnome.org/git/gimp\n ! [remote
rejected] master -> master (pre-receive hook declined)\nerror: failed to
push some refs to 'ssh://git.gnome.org/git/gimp'\n"”]
Any idea what's going on?
Is Icelandic missing from the LINGUAS-file?
If your translation is new, the Icelandic language code should be
added in the LINGUAS file. Currently DL can't do that automatically.
Ask someone with git access (team coordinator?) to do that manually.
Damned Lies can’t upload new translations in case of help documents.
Here a git hook needs to be adjusted by the admin.
I think Sveinn hit the problem of a new UI module with non-standard PO
directory ("po-windows-installer/") being declined by pre-receive hook
because it was not manually included as valid yet. I requested
sysadmins to adjust and it should be working fine now. At least, it
worked just fine for me, but it wasn't a new translation.
Sveinn, please try again.
To quote Damned Lies directly: "The file has been successfully committed
to the repository".
Thanks a lot Rafael.
Best ,
Sveinn
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating recipes
Þann fös 2.mar 2018 07:14, skrifaði Matthias Clasen: - We will not really be able to validate the text ourselves anymore (to fix spelling mistakes, punctuation, etc) - Translating such recipes will now require you to translate from your language to another (most likely, to English). We were wondering what you as translators think of these ideas ? Will you be able to help out with validating such content ? Will translating in the 'opposite direction' be a problem ? I seriously doubt that translating [thousands of] recipes should be within the scope of D-L translations, possibly a handful of them to populate an initial setup would be OK. Sveinn í Felli P.S: But in this case, I'd think about which format to use for exchanging recipes (I don't have gnome-recipes at hand); are the recipes sent in via database conduit or is it a XML-type of flat textfile? So, fabling a bit: At least SVG-style files can have language-dependent entities, so theoretically we can have entities filled in with any available language - even if the base language (English) is not present (I think). If each recipe is in a XML-format, it could be tagged with initial language, translated languages, locale dependent units, etc. A recipe-exchange server would tag recipes with available languages, people would download recipes in a language they understand and translate to another, resync, and voilá. Users (not GNOME-translators) would populate the translations step by step - but of course nothing guarantees the quality (spelling, etc.). We could end up by having a Wiki-eatia on our hands ;-) Of course this necessitates a recipe-editor supporting such handling of entities, same for parsing, etc. And probably this can be achieved via a database setup. Just thinking, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Is any translator team using glossaries?
Þann sun 29.apr 2018 20:32, skrifaði Rudolfs Mazurs: Hi all, I was looking around for a glossary for the GNOME project. The only one I could find was made 14 years ago [1]. Perhaps there is a more up-to-date version somewhere? You can roll your own using gettext [1], which calls them 'compendium' [2]. Beware, at first you may get a file with *all* existing strings in the project - what you really want is a selection of short definitions and words that are of help for translators. It can take several passes of gettext commands to filter out the relevant strings into a combined PO-file or a CVS (better for structuring). To use the glossary with a CAT-application like Lokalize, you would probably like to convert your glossary to a TBX-format (industry standard glossary exchange format); there are multiple tools available to help with glossary creation, but curiously most of them are Windows-only (Glossary Converter, Okapi-Rainbow, Heartsome-TMX...). Some of those run fine in Wine on Linux. OT: But you may also ask yourself *why* glossaries should be based on specific software-projects; for my (tiny) language, a coordinated effort has been made to publish sector/discipline-based glossaries [3]; one for each of astronomy, economics, engineering, electronics, etc. (total of 43 glossaries + a combined one I made myself). I even got separate glossaries for networking/encryption/certificates, for computers/software and for computers/hardware. Similar glossaries may exist for your language. Of course such field based glossaries have their disadvantages; designed by committees (when is that a good idea?), not always very up to date, difficult to amend/maintain/edit, etc. Meaning that there *has to be* active input from the users, which often are translators - professionals or hobbyists - who should listen carefully to their audience and be active in proposing new words/definitions to the publishers of the glossaries. Under no circumstances, these can exist as a private matter of some 'authority' in an 'ivory tower'... ;-) On the other hand such cross-projects glossaries can be of great help maintaining consistency across different projects, just as well as in a big project like GNOME. Just thoughts, best regards, Sveinn í Felli Translator for Icelandic (is) in several FOSS-projects [1]: <https://www.gnu.org/software/gettext/manual/gettext.html#Creating-Compendia> [2]: <http://docs.translatehouse.org/projects/localization-guide/en/latest/guide/project/howto.html#not-repeating-yourself> [3]: <http://www.malfong.is/index.php?lang=en&pg=islex> ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Is any translator team using glossaries?
Þann mán 30.apr 2018 20:41, skrifaði Rudolfs Mazurs: pirmd., 2018. g. 30. apr., plkst. 03:41 — lietotājs Rafael Fontenelle (< rafae...@gnome.org>) rakstīja: Well, I didn't know this glossary. Since I needed to build a glossary to ease the translation work, I started to use a script I maintain [1], based on a contribution by Daniel Mustieles, to download PO files of my language and create a local repository of translated fiels, which can easily searched with 'grep' or 'gtgrep' (from pyg3t). Currently I use a similar approach: I use lokalize tool to create translation memory and use it to search how strings are translated currently. Alas, this does not replace proper glossary, since translation memory tend to have errors and glossaries can be used more efficiently by lokalize tool. IMHO there's a big difference between a translation memory (TM) and a glossary. And TM's are different too: Lokalize has statistically defined TM's in databases, where some other CAT-tools use segment-based approach (e.g. OmegaT). The first approach is perhaps better suited for UI-translations, while the latter may be more effective for longer texts like documentation. (I still miss the old KBabel (precursor of Lokalize), where I could tune how close TM-matches should be, the number of letters in similar words, tight integration of many common tools, etc. and which had a bunch of validation tools for PO-files. But had its limitations too...) The use of a glossary is perhaps more related to spellchecking and grammar; it would be really nice if CAT-tools like Lokalize and PO-edit could underline texts (perhaps in blue) for which there are suggestions from a glossary (similar to the red underlining from a spellchecker). Anyway, entries in glossaries are mostly for reference/coordination and should be treated as such, in the end it's the translators choice how he styles the message to get the meaning across, right? Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Git access for translators
Þann þri 4.sep 2018 19:15, skrifaði Daniel Mustieles García via gnome-i18n: Ok so just to clear things and not to start a flame-war, I just want to use my script to commit a bunch of translations, only that. If i have to commit 20 PO files with just one string modified throught DL I will simply ignore them because all the click-work needed to do it it's not worth for me. +1 Upload of multiple files at once is crucial for language coordinators; regularly we have to introduce new/better terms/wordings *all over* the project. Not to mention cases like when someone replaces project-wide all triple points [...] with real ellipsis […], leaving hundreds of otherwise correct strings fuzzy - this has happened in other projects I've been working on. I only aim to work in translations and make my work as efficient as possible. Dont mind I have Git access or web access, but if I have to spend more time doing the commits manually than translating maybe we are doing something wrong. I agree we have always tried to reduce git access, but I think this case is more than justified to have it. And if you try the script to commit translations you will problably want to have git access to use it and not waste your time. Can you provide this features in DL today? API seems not be able to do that, so sorry for disagreeing again with you but currently DL is not usable for us to cover our needs. Best would be to add this feature through DL; Transifex has it via the tx-client, Pootle allows uploading of multiple ZIP-ed files (beware of keeping the file structure intact), KDE has synchronization via SVN. Most of the web-translation interfaces (Transifex, Crowdin, Weblate, etc.) also have a more/less functional search/replace for whole projects, which may in some cases might be substitute for multiple-file commits. Best regards, Sveinn í Felli Regards 2018-09-04 20:42 GMT+02:00 Alexandre Franke : On Tue, Sep 4, 2018 at 8:10 PM Daniel Mustieles García < daniel.mustie...@gmail.com> wrote: El mar., 4 sept. 2018 17:50, Alexandre Franke escribió: On Tue, Sep 4, 2018 at 9:30 AM Daniel Mustieles García via gnome-i18n < gnome-i18n@gnome.org> wrote: Damned lies has an API and your script could use it. If the API is not enough, we can extend it. Where is it documented? https://wiki.gnome.org/DamnedLies#XML_interfaces It doesn’t have any workflow actions exposed yet (so no commit), but that can probably be added. Is it compatible with bash scripts? It is a Web API. From bash you can use e.g. curl to make the calls. I've been using this script for several years without any problem, also mi Git access, and never received any disclaim about it, but thanks if I fixed a wrong string in docs... if game rules have changed due to gitlab migration maybe someone should explain them clearly... Don’t act as if we never said anything about trying to reduce direct repository access. We have always been trying to avoid giving access unless really necessary, and done everything we could to reduce cases where it was necessary. Rules have not changed, we just now have betters tools to enforce them. and then I could explain why this script is very useful for translators :-) I’m not claiming it is useless, but it is not the right way to do it. -- Alexandre Franke GNOME Hacker ___ 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: Translations for Glabels 4.0
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? 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? > ... 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/> Best regards, Sveinn í Felli Icelandic translator and coordinator in various FOSS-projects. 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translations for Glabels 4.0
Þann 1.11.2018 11:31, skrifaði Carmen Bianca Bakker: 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]. As I said, it's not overly complicated to convert between TS and PO: lconvert -if ts -of po -o application.po application.ts Translate with gettext-enabled tools, then convert them back using lconvert again: lconvert -if po -of ts -o application.ts application.po For this to work, you need Qt 4/5 Linguist tools set up. The question is whether this should be scripted on the server side, so that people opting for off-line translation could download their preferred format - or if everyone should do it on their own? There are translation platforms where the functionality is built-in; I know that Transifex does, pretty sure that Weblate and Crowdin can also. P.S: Apparently parts of KDE are nowadays delegated to pure Qt, meaning that some buttons/dialogs must be translated in Qt itself. The Qt people support much fewer languages than KDE or Gnome, so that can be a problem in itself if you're translating some minor language... Best regards, Sveinn í Felli ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translations for Glabels 4.0
Thanks Mario, concise and clear. Best, Sveinn Þann 1.11.2018 12:19, skrifaði Mario Blättermann: 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: Wrong context in 2 strings
Since it's a change in context and not in the translatable string, it would be awful to fuzzy all those translations just because there's a change in a path/pointer. E.g. anything in a '#: ../src/aisleriot.schemas.in.h:1' comment could be altered as suits the programmer since it doesn't touch the string or the translation. And preferably via search-and-replace. Just thoughts, Sveinn í Felli Þann 7.2.2019 15:32, skrifaði Daniel Mustieles García via gnome-i18n: If the original string doesn't change and indeed it doesn't implies a change in the translated one (and avoids translators to review a fuzzy string) it's ok for me to apply the change directly in PO files. Maybe other coordinators will disagree, but you have the OK to do it in the Spanish PO file ;-) About the second question... don't know how often this issues are, but I would ask here before commiting, just to ensure you have the OK from the i18n community. Thanks! El jue., 7 feb. 2019 a las 16:12, Jehan Pagès via gnome-i18n (< gnome-i18n@gnome.org>) escribió: Hi! In GIMP, we had a small bug in 2 strings: "Grow lighter areas of the image" and "Grow darker areas of the image". Basically in our code, we declared the strings with "drawable-action" context (hence that was the msgctx registered in po files) but called the translation with "filters-action" context so they were not translated. I fixed the code to use "filters-action" everywhere (the other was wrong), but the wrong context is now in various po/*.po files (43 files). Do you mind if I just do a massive search-and-replace for these 2 context/strings to fix them? I mean, I actually already did it locally (took 20 secs), and I think that it is simpler than having everyone just edit manually for what was basically just a code bug. The actual context is the same (these strings are filter descriptions, same place in the GUI as what they were, nothing changed GUI-wise). So that looks harmless to me. Yet I have been told we should not touch the po files ourselves, if possible. So 2 questions: 1/ Is it ok if I just push this change? 2/ In the future, what should be our process as developers when we just see these kinds of code issues affecting the po files? Can we just push (making our own decision that this is not a translation issue) or we must ask case by case? Thanks for the awesome work, all! Jehan -- ZeMarmot open animation film http://film.zemarmot.net Liberapay: https://liberapay.com/ZeMarmot/ Patreon: https://patreon.com/zemarmot Tipeee: https://www.tipeee.com/zemarmot ___ 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 3.32 release notes are finalized
Yesterday I could submit once to repository on a previously non-translated module (Damned Lies itself) for Icelandic; DL took less than a minute before displaying the new strings (cool...), but subsequent submissions timed out. No warnings, whatsoever. The file passes 'msgfmt -vc' and the header seems OK. Meanwhile other modules behave correctly (e.g. GIMP) so I can submit to repo as needed. Not sure if this is related, but nevertheless still a problem. Best regards, Sveinn í Felli Þann 14.3.2019 07:23, skrifaði Daniel Șerbănescu: În data de Jo, 14-03-2019 la 00:09 +0200, Mart Raudsepp a scris: Ühel kenal päeval, K, 13.03.2019 kell 18:34, kirjutas Rafael Fontenelle: Daniel, It should work now. I was able to submit the translation to repository. You have tag instead of in the introductory text about Taipei in there. It seems to have broken hosted release notes for a bit, though they (currently) mysteriously reappeared afterwards. In either way, it doesn't pass yelp-check validate right now. Mart There are still errors committing from Damned Lies. Now the "Submit to repository" appears in the dropdown but when I choose it it fails. This is the complaint: A apărut o eroare în timpul aplicării acțiunii: Comiterea nu a reușit. Eroarea a fost: „[Errno 1] Command: "['git', 'commit', '-m', 'Update Romanian translation', '--author', 'Daniel Șerbănescu ']", Error: hint: The '.git/hooks/pre-commit' hook was ignored because it's not set as executable. hint: You can disable this warning with `git config advice.ignoredHook false`. ” The first part translates as "There was an error while applying the action: Commit failed. The error was..." I tried to commit manually via git but I still get: «««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.»»» Regards Daniel ___ 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: Error in simple-scan
Hi, I get this error for gimp.master: "“[Errno 1] Command: "['git', 'commit', '-m', 'Update Icelandic translation', '--author', 'Sveinn í Felli ']", Error: b'# On branch master\n# Untracked files:\n# (use "git add ..." to include in what will be committed)\n#\n#\tbuild/flatpak/flathub/\nnothing added to commit but untracked files present (use "git add" to track)\n'”" Spooky...? Sveinn í Felli Þann 12.12.2020 12:58, skrifaði Enrico via gnome-i18n: Hello folks When tried to send simple-scan translation via Damned Lies received the same error as reported previously in the email thread: “[Errno 1] Command: "['git', 'push', 'origin', 'master']", Error: Warning: Permanently added 'gitlab.gnome.org,172.31.2.39' (ECDSA) to the list of known hosts. remote: GitLab: You are not allowed to push code to protected branches on this project.To g...@gitlab.gnome.org:GNOME/simple-scan.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'g...@gitlab.gnome.org:GNOME/simple-scan.git' ” May someone please assist me on pushing simple-scan pt_BR translation to repository? Thanks in advance, Enrico. Em 02/12/2020 11:16, Jonas Ådahl via gnome-i18n escreveu: On Wed, Dec 02, 2020 at 04:13:16PM +0200, Yuri Chornoivan via gnome-i18n wrote: середа, 2 грудня 2020 р. 16:09:37 EET Jonas Ådahl написано: On Wed, Dec 02, 2020 at 03:48:19PM +0200, Yuri Chornoivan via gnome-i18n wrote: середа, 2 грудня 2020 р. 15:38:57 EET Daniel Mustieles García via gnome-i18n> написано: Hi, I've got the following error when trying to upload a translation for simple-scan, using Damned Lies: «[Errno 1] Command: "['git', 'push', 'origin', 'master']", Error: Warning: Permanently added 'gitlab.gnome.org,172.31.2.39' (ECDSA) to the list of known hosts. remote: GitLab: You are not allowed to push code to protected branches on this project.To g...@gitlab.gnome.org:GNOME/simple-scan.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'g...@gitlab.gnome.org:GNOME/simple-scan.git' » Could someone please review it? Thanks in advance Hi, The master branch for mutter is locked as well, btw. Can you try again? It seems it was changed to only allow pushing from maintainers, but the original intention was to only restrict merging merge requests, as we've moved to using marge-bot. I've now changed the setting to limit merging to maintainers, but pushing to maintainers and developers as was the case before. Jonas Yes, it works now. Many thanks for your help. No problem, thanks for testing, and sorry about the misconfiguration! Jonas Best regards, Yuri ___ 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Shortcuts in DL workflow
Þann 7.11.2021 09:41, skrifaði Claude Paroz: Dear translators, Following the issue opened by Yaron [1] about DL, I'd like to suggest some modifications to the traditional Web translation workflow: - Allow to submit a translation or a review directly without passing through the reserve step. The reserve step still remains, of course, but would be optional. - Allow a committer to Submit to repository as soon as a .po file is available in the workflow, without requiring a review or a Ready for submit action. This would shorten the minimal number of required form submits to 2 (upload the translation / submit to repository). What do you think about this. I have the feeling that it would be an answer to a concern that several coordinators have expressed in the past, especially for smaller teams. Kind regards, Claude [1] https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/268 Yes, please; this would be of great service to us, one-man teams, who don't have to ask ourselves for revisions or permissions to proceed ;-) But mostly it's a question of ergonomics and health issues (wrist strain)... My dream is of course to be able to upload multiple files at once, especially after correcting/adapting/streamlining a term in various files, or when some dev has fuzzied a bunch of strings in plenty of places (applying typographic conventions, updating notions of years, or just some cosmetic features). I won't mind if this is a ""shortcut" for trusted translators/proofreaders", depends though on the definition of who would be those trusted translators/proofreaders. Best regards, Sveinn í Felli Icelandic translator ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Secrets 6.0 release
Is this an adequate venue for quickly discussing ambiguous strings like this one: "Please Wait. Another Save is Running." Is there another 'Save'-action running, or is there a typo 'Save' --> 'Safe' ? Best, Sveinn í Felli Þann 7.1.2022 18:22, skrifaði Maximiliano Sandoval via gnome-i18n: Dear Translators Secrets¹, formerly Password Safe, got its 6.0.beta release today and it is in string-freeze, the plan is to release 6.0 next Friday containing only bug-fixes, if any, and translations. 1. https://l10n.gnome.org/module/secrets/ Thanks! Maximiliano ___ 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: Can't submit gnome-nibbles and iagno po files
I'm also getting error while submitting iagno.master.po through Damned Lies: “[Errno 1] Command: "['git', 'push', 'origin', 'master']", Error: Warning: Permanently added 'gitlab.gnome.org' (ED25519) to the list of known hosts. remote: fatal: bad object refs/pipelines/381544 fatal: bad object refs/pipelines/381544 To gitlab.gnome.org:GNOME/iagno.git ! [remote rejected] master -> master (missing necessary objects) error: failed to push some refs to 'gitlab.gnome.org:GNOME/iagno.git' ” This has been persistent for at least a month. Any solution? Best, Sveinn í Felli Þann 30.7.2022 14:05, skrifaði Claude Paroz: Le 29.07.22 à 13:49, Нарт Лӏыша via gnome-i18n a écrit : Hello, I can't submit the following files: 1. gnome-nibbles.master.po 2. iagno.master.po I m getting the following errors: Screenshot from 2022-07-29 11-01-55.png Screenshot from 2022-07-29 11-05-50.png What could be a possible solution? Could you try again, please? Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Totem branched for 2.28
Hi, Philip Withnall wrote: > On Tue, 2009-09-29 at 00:36 +0200, Gil Forcada wrote: >> El dl 28 de 09 de 2009 a les 23:34 +0100, en/na Philip Withnall va >> escriure: >> >>> Note that I had to fiddle with the Plural-Forms headers in the >>> Icelandic, Malay and Uighur translations before I could push the branch. >>> Uighur in particular needs some attention, since I had to make up a >>> plural form. >> Did you filled bugs against those translations teams to let them know >> about it? > > I don't think the Icelandic or Malay problems need bugs filing, since I > was able to copy their Plural-Forms header from other .po files/Damned > Lies, so it should be correct. Any affected plural strings I've marked > as fuzzy. > I see in the new icelandic totem.po a huge string for plurals: Plural-Forms: nplurals=2; plural=(n % 100 != 1 && n % 100 != 21 && n % 100 != 31 && n % 100 != 41 && n % 100 != 51 && n % 100 != 61 && n % 100 != 71 && n % 100 != 81 && n % 100 != 91);\n Normally we use: Plural-Forms: nplurals=2; plural=n != 1;\n Actually there's a bigger problem with the icelandic translations; almost all recent translations are not merged into the actual/updated po file, they just lie in DL like sitting ducks along with the old po. Maybe this is a question of manually pushing the merger, but anyway I don't know how this should work, being a plain mortal translator w/o git or svn/cvs. I've contacted the is-coordinator and filed a bug but no-one seems to be able to push those translations. Among them were totem and totem-pl-parser which still has the plural bug - corrected by me quite a long time ago. If there is a howto describing handling of translations in DamnedLies (for translators), I'd appreciate a link. Cheers, Sveinn í Felli > I would like to file a bug against the Uighur (ug) translation, but it > doesn't have a component under l10n on b.g.o. :-\ > > Philip > >> Regards, >> >>> Thanks, >>> Philip >>> ___ >>> 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 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
