commit 5c0fc54f59ba5d8d04871d4695ac8f06bd166c45 Author: emma peel emma.peel@riseup.net Date: Fri Jan 10 15:37:33 2020 +0100
better order and change of link. also please check if your ticket exists before opening it :D --- content/localization/translation-problem/contents.lr | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/content/localization/translation-problem/contents.lr b/content/localization/translation-problem/contents.lr index 242c109..26ce65a 100644 --- a/content/localization/translation-problem/contents.lr +++ b/content/localization/translation-problem/contents.lr @@ -20,5 +20,6 @@ body:
* If you are already a [Tor translator](../becoming-tor-translator), you can simply find the string and fix it in [transifex](https://www.transifex.com/otf/torproject/). * If you don't know how to find the string to fix, you can [open a ticket on our Bugtracker](https://support.torproject.org/misc/bug-or-feedback/), under the **Community/Translations** component. -* You can report such issues on [irc](https://webchat.oftc.net/), on the #tor-l10n channel (you may need to be registered to log in). + Before opening a ticket, see the currently [open tickets for Translations](https://trac.torproject.org/projects/tor/query?status=accepted&status=as...) because maybe it is already reported. * You can send an email to the [tor localization mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n). +* You can report such issues on [irc](https://support.torproject.org/get-in-touch/#irc-help), on the #tor-l10n channel on the oftc network (you may need to be registered to log in).