After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 628890 - WebkitGTK+ bug reports at bugs.webkit.org are not being processed
WebkitGTK+ bug reports at bugs.webkit.org are not being processed
Status: RESOLVED FIXED
Product: damned-lies
Classification: Infrastructure
Component: l10n.gnome.org
unspecified
Other Linux
: Normal normal
: ---
Assigned To: damned-lies Maintainer(s)
damned-lies Maintainer(s)
Depends on: 628871
Blocks:
 
 
Reported: 2010-09-06 14:08 UTC by Simos Xenitellis
Modified: 2016-08-11 16:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Simos Xenitellis 2010-09-06 14:08:44 UTC
Translators are submitting bug reports to bugs.webkit.org but the developers there are not taking care of them.

See
https://bugs.webkit.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=WebKit&content=translation

There are at least 12 translations in the backlog.
Comment 1 Claude Paroz 2010-09-06 14:41:51 UTC
Gustavo (cc), what can we do about this? Could it be possible to appoint one GTP member with rights to submit translations in WebkitGTK+ SVN module?
Comment 2 Gustavo Noronha (kov) 2010-09-07 13:25:24 UTC
I am usually the one who takes care of translations, the problem is I don't have a good way of watching when new translations arrive. If people can CC me when they report the bug, I promisse I'll get them landed in a quicker fashion. I'll go through that search you made tonight.
Comment 3 Simos Xenitellis 2010-09-07 13:32:03 UTC
Gustavo, you need to create a component on the WebKit bugzilla and become the owner of that component. Then, translators would simply need to report the bug on webkit, component: (let's say) 'l10n' and you will be notified by e-mail.

We then update the webkit description on l10n.gnome.org with the above instructions.
Comment 4 Gustavo Noronha (kov) 2010-09-07 14:42:47 UTC
That is true, I will check with the bugzilla admins if we can create an webkitgtk-l10n component.
Comment 5 Wouter Bolsterlee (uws) 2010-12-17 00:55:19 UTC
Gustavo, any progress on this? Gnome i18n people would be very happy if you can sort this out...
Comment 6 Chris Leonard 2012-05-04 22:54:23 UTC
Gustavo, I believe you may have addressed this by setting up an alert for yourself when a new webkitgtk+ L10n bug is filed on the webkit bug tracker.  Is that working now, allowing this bug to be closed?
Comment 7 Claude Paroz 2012-10-24 06:52:54 UTC
Now that the POT file is again buildable, let's wait and see if translations are committed in an acceptable time frame...
Comment 8 Muhammet Kara 2016-01-09 20:43:25 UTC
The last Turkish translation was committed in about three weeks. (Not too long I think.)

Let's see if this one gets into svn in a timely manner: https://bugs.webkit.org/show_bug.cgi?id=152948
Comment 9 Muhammet Kara 2016-01-09 23:48:48 UTC
It has already been committed to the repository.[0] It took less than three hours for the bug report to be handled. Should we close this bug report?

[0] http://trac.webkit.org/changeset/194822
Comment 10 Piotr Drąg 2016-08-11 16:39:49 UTC
Michael and other developers are doing a great job. Closing the bug.