Errors on translated blog posts at geti2p.net #43
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Opened 7 years ago
Last modified 3 years ago
#1396assigneddefect
Errors on translated blog posts at geti2p.net
Reported by:rOwned by:slumlord
Priority:
minor
Milestone:
Component:
www/i2p
Version:
0.9.15
Keywords:
error
Cc:
sadie
Parent Tickets:
Sensitive:
no
Description
Errors at
https://geti2p.net/ru/blog/post/2014/03/12/press-release-ddg-donation
https://geti2p.net/de/blog/post/2014/03/12/press-release-ddg-donation
and other already translated languages.
System Message: ERROR/3 (/opt/i2p.website/i2p.www/i2p2www/blog, line 10); backlink
Unknown target name: "nominations".
Subtickets
Still an issue. These are the parts that are translated:
Has this been resolved?
comment:4 Changed 3 years ago by slumlord
Don't know if this error has re-appeared anywhere else. From what I am able to gather, things like links, etc. should be kept out of the
{% trans -%}/{%- endtrans %}tags so that they don't get translated by the translation team?Perhaps a set of guidelines when blog posts are drafted and added to the website system to ensure that the
{{ link }}style of links aren't included, or a way of tagging such links so that translators know not to translate them.comment:3 Changed 3 years ago by zzz
Cc:sadie added
Owner:
set to _slumlord_Status:new →
assigned
comment:2 Changed 6 years ago by str4d
Summary:Errors on translated pages at geti2p.net →
Errors on translated blog posts at geti2p.net
comment:1 Changed 6 years ago by str4d
Keywords:error added; website translations removed
Milestone:0.9.16
The root cause of blog translation errors is either incomplete translations, or mistakes in the reStructuredText formatting in the translation. In the cases above, the translators have translated the rST tag corresponding to the link, but haven't translated the paragraph that uses it; the Docutils backend can't connect the link to the paragraph (which is done by exact text match) and panics.
The immediate solution is to manually fix these errors as they appear. The long-term solution is to educate the translators about blog translations, to help them prevent these errors from occurring.
This ticket will remain open until the long-term solution is successfully implemented. In the meantime, please continue to post blog errors in this ticket. I think I will even adjust the blog error message to reference this ticket, so viewers know where to post errors.