Skip to content

Translate 2025 Third Parties chapter to Turkish - #4556

Merged
tunetheweb merged 1 commit into
HTTPArchive:mainfrom
MuslumYilmaz:tr-2025-third-parties
Nov 3, 2026
Merged

tunetheweb merged 1 commit into
HTTPArchive:mainfrom
MuslumYilmaz:tr-2025-third-parties

Conversation

@MuslumYilmaz

Copy link
Copy Markdown
Contributor

Makes progress on #1044

This is the first Turkish chapter in the repo, so it is also the first time src/templates/tr/base_chapter.html gets rendered.

Changes:

  • src/content/tr/2025/third-parties.md: Turkish translation of the 2025 Third Parties chapter.
  • src/templates/tr/base_chapter.html:
    • Line 7 never compiled. It had ’ın outside the string, which Jinja rejects with TemplateSyntaxError: unexpected char '&'. Behind that, + year applied a unary plus to a string, which raises TypeError. Without the fix the chapter page would return a 500. The line now follows the English template.
    • Lines 25-26 fix the keyboard tooltips. Next said ',' instead of '.', and both are reworded.
  • src/templates/tr/base.html:
    • The chapter navigation name goes from "Üçüncü Partiler" to "Üçüncü Taraflar", so it matches the H1, which comes from the frontmatter title.
    • The figure label goes from "Figure" to "Şekil", matching the "Şekil" already used in the two macros below it.
  • src/config/contributors.json: translator entry for MuslumYilmaz, placed alphabetically by first name.

Notes:

  • %90 puts the percent sign first, which is the Turkish convention.
  • The 2024 links carry hreflang="en" because there is no tr/2024 chapter, so they redirect to English.
  • The GDPR link points to the Turkish Wikipedia article.
  • In the English line 176 the label says "non-USP Standard", but the text means a non-standard USP. The Turkish uses the latter. I can fix the English label in this PR too if you'd like.
  • The description has no apostrophe on purpose. An apostrophe ends up double-escaped as ’ in the meta, og, twitter and JSON-LD tags, as can be seen live on it/2022/css.

@MuslumYilmaz
MuslumYilmaz requested a review from a team November 3, 2026 05:16

@tunetheweb tunetheweb left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the translation and the corrections!

The 2024 links carry hreflang="en" because there is no tr/2024 chapter, so they redirect to English.

This is a tricky one. While this is technically correct, it does require remembering to update this is in the future if we ever add it. So until not we're not done this under the not-very-convincing thought that it links to the Turkish version, it just doesn't exist yet and is redirected to the English version in the meantime.

In the English line 176 the label says "non-USP Standard", but the text means a non-standard USP. The Turkish uses the latter. I can fix the English label in this PR too if you'd like.

Not an expert on English grammar (and certainly not on USP) but as a native speaker I think either works in English to be honest. It's still checking the us_privacy parameter (which is the USP Standard with a capital S). "non-standard USP Standard" as given in the text itself is probably most accurate, if a bit of a mouthful. Anyway happy to go with what you have here.

The description has no apostrophe on purpose. An apostrophe ends up double-escaped as ’ in the meta, og, twitter and JSON-LD tags, as can be seen live on it/2022/css.

To me that's a failure of the receiving client and they should be HTML encoded. But sometimes it's not worth the fight! :-)

Anyway, happy to merge this and will do so tomorrow unless you have any further comments on the above?

@MuslumYilmaz

Copy link
Copy Markdown
Contributor Author

Thanks for the review and the context! No further comments from my side, happy for it to be merged :)

@tunetheweb
tunetheweb merged commit 1e6f734 into HTTPArchive:main Nov 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants