Repository navigation
i18n: polish Turkish engine names and add release notes for 2.1.0 & 2.0.0 - #718
Conversation
|
Thanks, @Armone0! I pushed two small changes to the release notes, where the Turkish said a bit more than the English:
One question, no change needed if you're sure: in a computer context, could "HWPX yazıcı" / "DOCX yazıcı" be read as a printer ("sanal PDF yazıcısı")? These engines write HWPX / DOCX files. If "yazıcı" is the natural word for that in Turkish, we'll keep it as you wrote it. |
52edbe3 to
b01ac7b
Compare
…o from a video; 'oluşturucu' for the HWPX and DOCX writers Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks @KnifeLemon! You are completely right. In Turkish, "yazıcı" is overwhelmingly understood as a hardware or virtual printer (like a PDF printer driver). Using "HWPX oluşturucu" and "DOCX oluşturucu" (builder / generator) is much more natural, accurate, and completely avoids any confusion with printers. The changes you pushed look great to me! 🙏 |
|
Thanks for confirming, @Armone0! I'll merge once CI is green. |
What does this change?
tr.jsonfrom English /(built-in)to Turkish(yerleşik)(e.g.Markdown (yerleşik),Elektronik tablolar (yerleşik),Arşivler (7-Zip)).tr:) to the<!-- update -->blocks of versions 2.1.0 and 2.0.0 inCHANGELOG.mdso the in-app update card displays localized notes when updating from older versions.Type of change
Checklist