Translation via Crowdin - Old text and fuzzy not available

CyrilleB79 commented 11 months ago

I am experimenting with new translation framework with French translation. I am accessing the Crowdin translation via poedit.

Steps to reproduce:

Open new Crowdin translation with poedit
Look at string "Portable directory:"; this string has been slightly modified from 2023.3 to 2024.1; only the "&" character has been modified.
Press shift+control+O

Actual behavior:

The "old text" with "&" character should be reported.
The "Need work" checkbox (fuzzy) should also be checked.

When merging manually in poedit the .pot into nvda.po of 2023.3, I get this item:

#. Translators: The label of a grouping containing controls to select the destination directory
#. in the Create Portable NVDA dialog.
#: gui\installerGui.py:362
#, fuzzy
#| msgid "Portable &directory:"
msgid "Portable directory:"
msgstr "&Répertoire portable :"

Expected behavior:

The old source text should be available. I did not check if it is on the webpage of Crowdin.
The "Need work" checkbox (fuzzy) should be checked.
The old translated text should still be there so that I can modify it just removing the accelerator key.

The Crowdin file saved via poedit indicates the following:

#. Translators: The label of a grouping containing controls to select the destination directory
#. in the Create Portable NVDA dialog.
#: gui\installerGui.py:362
msgid "Portable directory:"
msgstr ""

NVDA logs, crash dumps and other attachments:

N/A

System configuration

NVDA installed/portable/running from source:

N/A

NVDA version:

2024.1beta1

Windows version:

N/A

Name and version of other software in use when reproducing the issue:

Poedit, Version 3.4.1 (6867)

Other information about your system:

N/A

CyrilleB79 commented 11 months ago

Cc @michaelDCurran

michaelDCurran commented 11 months ago

Unfortunately it looks like that Crowdin does not support fuzzy translations in PO files. However, within the web interface, its translation memory feature does try to find similar strings I believe. I appreciate that this feature in PO files did save time for strings that changed in a small way. Question is whether this is a critical limitation or something that can be worked around.

CyrilleB79 commented 11 months ago

My opinion is that it's probably not critical. But opinion from other persons in the translators community would be appreciated.

Though, having this possibility allows to avoid unexpected change in the GUI, e.g.: Let's imagine that you have:

2023.3: "Portable &directory" translated to "&Répertoire portable"
2024.1: "Portable directory" translated to "Dossier portable" ("Dossier" stands for "Folder" and is often used interchangeably with"Répertoire" = "Directory")

Having the old text would have helped to avoid changing the word in the GUI with a synonym just to remove an accelerator.

Can we ask Crowdin to add this possibility, hoping it can be available in the future? If yes and if you do such request, please add the link here for tracking.

Adriani90 commented 11 months ago

Actually in the crowdin website editor you can apply an advanced filter on the strings called "modified source strings" so i guess this would only show the modified source strings but yeah i guess you would not see the old text but this is not really critical in my view as well. There is a way to view the string history for translated strings but not for source strings. So maybe this could be requested at Crowdin. they seem to be very responsive per Email at least.

nvaccess / nvda