Opened 2 months ago
Last modified 2 months ago
#5510 new defect
Translation of the "Topics" string not taken into account in the French handbook
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Handbooks | Keywords: | has-screenshots needs-patch |
Cc: |
Description
Hi,
In our handbook, the translation of string "Topics" isn’t taken in account.
Yet this string is translated: see https://translate.wordpress.org/projects/meta/forums/fr/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=218989&filters%5Btranslation_id%5D=10396893
According to @audrasjb, the bug is in this file: https://meta.svn.wordpress.org/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-helphub/inc/table-of-contents-lite/includes/class-table-of-contents-lite.php
See an example: https://fr.wordpress.org/team/handbook/guide-du-traducteur/le-glossaire-et-les-erreurs-de-traduction-les-plus-frequentes/
Thank you for your attention.
Attachments (1)
Change History (5)
#1
@
2 months ago
- Keywords has-screenshots needs-patch added
Thanks for opening this ticket @jdy68 !
Yes, that's an issue, and I guess that file is not a problem by itself, but more the text-domain of the related plugin: table-of-contents-lite
It should be changed to be consistent with the related wporg text domain.
https://meta.svn.wordpress.org/sites/trunk/wordpress.org/public_html/wp-content/plugins/support-helphub/inc/table-of-contents-lite/table-of-contents-lite.php
Cheers,
Jb
#2
follow-up:
↓ 3
@
2 months ago
The problem is that the Support Forums localisation isn't loaded on P2 Handbook pages.
The handbook plugin pulls in the HelpHub TOC code, but doesn't load the required textdomains for it.
I recently noticed this, but didn't click that handbooks were in use on non-support localised sites ('duh, of course they are!)
Changing the localisation to wporg
won't work as intended, but it might be worth just duplicating some of the TOC code between them, or allowing for a translated string to be passed to it.. or just loading the right textdomain..
#3
in reply to:
↑ 2
@
2 months ago
Replying to dd32:
Changing the localisation to
wporg
won't work as intended, but it might be worth just duplicating some of the TOC code between them, or allowing for a translated string to be passed to it.. or just loading the right textdomain..
Ah yes, by wporg
, I meant use a the correct/related wporg-like
text-domain :)
Is this plugin available in the repository? Maybe we can also translate it directly?
An example of no translation