Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add-ons French translation + lots of language file enhancements #466

Open
Lidgeu opened this issue Aug 15, 2021 · 86 comments
Open

Add-ons French translation + lots of language file enhancements #466

Lidgeu opened this issue Aug 15, 2021 · 86 comments

Comments

@Lidgeu
Copy link

Lidgeu commented Aug 15, 2021

Hello Gaku,

I recently discovered - and adopted, TablacusExplorer - and its numerous useful add-on's ;o)

  1. Almost all the add-on's I'm using are not translated in French. I did the job for these ones --> TabacusExplorer_Addons-FR.zip

  2. While exploring Tablacus functions, despite the outstanding translation made by your official translator "Olivier Wuillemin/bufferUnderrun", I discovered a couple of mistakes (inversion, wrong French wording, etc.).
    For my own usage, I adapted the fr.xml file --> fr.xml-PLL.zip. Here is the list of the "corrections" I did --> FrenchLanguageCorrections.txt

  3. For your information, I also noticed that a couple of texts are not available to the translators : TranslationsMissing.pdf

For your best usage ;o)
I'm ready to cooperate more, if you need / want. :o)

Pierre
@tablacus
Copy link
Owner

Thank you sooo much!!

@Lidgeu
Copy link
Author

Lidgeu commented Aug 16, 2021 via email

@tablacus
Copy link
Owner

Is French word for "Swap" "Échanger"?

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Aug 17, 2021

Is French word for "Swap" "Échanger"?

Regards,

In computer sciences / programming related messages, the French word "Permuter" is more appropriated ("Echanger" is mainly used in trading, banking, ...).

By the way, I just update to 21.8.16 and find this :

  1. undoclosetab add-on do not load the fr.xml language file.
    undoclosetab-missing
    But if you use the "French localized" config.xml I sent, it's OK.

  2. In the treeview preference, I discovered this, which perhaps escaped to my previous check :
    treeview-missing
    ... and not found where to translate it !!
    Literally, this can be translated by "La racine est dépliée" or "Racine dépliée", but as I did not exactly identified what is used for, I cannot fully validate this wording ;o)

Regards,
Pierre

@ccfs
Copy link

ccfs commented Aug 19, 2021

  1. & (&) indicates that the next character is a shortcut to a menu item. You have to include it in translated text.

<text s="&amp;Undo close tab">Défaire la fermeture d'onglet</text>

  1. "Root has expando" - add an expand/collapse button to tree root

exp

@Lidgeu
Copy link
Author

Lidgeu commented Aug 19, 2021 •
edited
Loading

1- undoclosetab : corrected, working, French version --> undoclosetab_1.14-FR-210849.zip

2- "Root has expando", in French : "Racine repliable/dépliable" . French localization adapted here --> fr.xml-21.8.19.zip
(+ one correction "click" to "clic")
:o)

@Lidgeu
Copy link
Author

Lidgeu commented Oct 30, 2021

My Gihub logging issue being solved (my mistake), I'm posting here, for the community, the appropriate part of the email I sent to you a couple of hours ago ;o) ​
It consists of 2 updates and 1 new translation (created since TE21.10.8 and checked with last 21.10.27 version).

AddonsDeleteSegoe

  1. Update - fr.xml-21.10.8.zip : Since this version, I noticed that the translation of "Delete" ("Supprimer") was not anymore loaded (?). I adapted the French file with a shorter French word "Retirer". Strictly speaking, "Retirer" means "Remove" but the average French user will better understand this vs "Delete" 😉
  2. New - segoeicons-2021.9.5-FR-config.zip : The French language is added to this addon. WARNING : in the xml file, the <en> tag is also applied on the <jp> / <zh>(I think) translation ;o)

AddonsRetirerDeleteSegoe

The third file, tabplus-config-optionshtml.zip, is a (personal) update as the option.html file is not multilingual. This is for your best usage.

tabplus-config-optionshtml.zip
segoeicons-2021.9.5-FR-config.zip
fr.xml-21.10.8.zip

Best regards

@ccfs
Copy link

ccfs commented Nov 1, 2021

Any translation must be UNIQUE. Since both "Remove" and "Delete" are translated to "Supprimer", the translation for "Delete" is dropped by TE silently. Using another word ("Retirer") is a correct move.

TE add-ons are multilingual (in almost all cases). You need not prepare any language-specific "option.html" file. Instead, you should translate based on the XML file in LANG sub-folder. Unfortuntly Gaku does not provide any for tabplus add-on (and many others).

By the way, I think the current method - distributing translations in every add-on - is bad. It causes headaches in the deployment of translations. A better method is to centralize all translations for TE and all add-ons of each language in one XML file in TE LANG folder.

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Nov 1, 2021

See the italic text ;o)

Any translation must be UNIQUE. Since both "Remove" and "Delete" are translated to "Supprimer", the translation for "Delete" is dropped by TE silently. Using another word ("Retirer") is a correct move.
-->Got it ! I (re)adapted the French translation in order to respect the correct "Delete / Supprimer" and "Remove/Retirer" matching. Work perfectly now with this file : fr.xml-21.11.08.zip

TE add-ons are multilingual (in almost all cases). You need not prepare any language-specific "option.html" file. Instead, you should translate based on the XML file in LANG sub-folder. Unfortuntly Gaku does not provide any for tabplus add-on (and many others).

By the way, I think the current method - distributing translations in every add-on - is bad. It causes headaches in the deployment of translations. A better method is to centralize all translations for TE and all add-ons of each language in one XML file in TE LANG folder.

--> On one hand, centralizing all TE adds-on translations in the same folder than the program one looks like more efficient, despite generating automatically an update at each new or main improvement of add-on.
On the other hand, the users are downloading only the adds-on the need/like/select. So they don't want to "overload" their system with translations useless for them. The current procedure ensure them the delivery of a full autonomous multilingual add-on.
Right ?

Regards,

@ccfs
Copy link

ccfs commented Nov 2, 2021

There are about 200 translation lines in a TE language file. I have fully translated TE and (almost) all add-ons to Traditional Chinese, resulting in about 580 lines. I don't see any adverse effect to my system.

By centralizing all translations for each language to a single file, the deployment of a language becomes highly simplified. No version change to an add-on is required, if you do not translate the almost-useless description (I suggest to change the "Details" button on "Tools > Add-ons" page to a hyperlink to Wiki, to get rid of the description).

This will certainly lower the autonomy a bit, but all users will benefit by the simplified procedure.

I have imported your French translations into an LibreOffice spreadsheet file and have produced a French language file "PLL.xml". Try it and you will understand my suggested procedure. Translation for "Force refresh" add-on, which you made in August but is never available, is also there.

There are 2 translations to "Exécuter", so one of them will be dropped. You need to correct that and update your language file. See "Full translation of TE and add-ons #220" for the steps. Note that the spreadsheet file now contains a "user-defined function" to produce XML lines. Enable macro to make it works.

PLL.zip

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Nov 4, 2021 via email

@Lidgeu
Copy link
Author

Lidgeu commented Nov 11, 2021 via email •
edited
Loading

@ccfs
Copy link

ccfs commented Nov 12, 2021

@Lidgeu,

Sorry I cannot find any attachment. Did you miss them?

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Nov 12, 2021 via email

@ccfs
Copy link

ccfs commented Nov 13, 2021

@Lidgeu,

Sorry still nothing, including the screen capture you mention above. I cannot find the attachments from my gmail too.
Maybe you have to solve the firefox problem first. Some posts on the internet state that it is due to DNS or profile.

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Nov 13, 2021

@ccfs ,
According my last mail (today earlier) to "info@...", I inserted the lost attachments in updating my post here above.
Regards,

@tablacus
Copy link
Owner

Gmail has strict standards for attachments, you're better off writing directly to the GitHub Issue.

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Nov 14, 2021 via email

@ccfs
Copy link

ccfs commented Nov 15, 2021

@Lidgeu,

You should not translate "Get %s..." to "Obtenir des icônes ...". You must keep %s which will be replaced by something at runtime. For example, on the options page of "Download" add-on, %s will be replaced by cURL and Wget.
Download

To solve the case problem of "Get Icon", I suggest to enhance TE to make that an independent caption, so that it can be independently translated. Same for "Tool bar Icon".

Regarding the ODS file:

  • "^Arrange by:" is in the tip pop-up of the Sort button. "^Name" to "^None" are in the menu of the button. They are already translated by TE. I include them in the ODS file for completeness. You need not (and cannot) translate them.
    Arrange by
    sort-button

  • 6 add-ons dated 2020/6/17 and before cannot work with Edge Blink engine. If you have installed WebView2 extension, such add-on will be marked as "Incompatible".

  • "RunAs" appears in the drop-down of "Type".
    RunAs

  • "Root has expando" was unexpectedly changed to "Root" since TE 21.8.19. The translation is now unusable. See "Inappropriate caption changes in TE 21.8.19 #468"

TE has been developing for many years. However, the English language file has seldem been updated. Some translation lines are disused and many are added. The language files for many add-ons are even missing. Appearantly some translators have found this problem, but the application owner has not.

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Nov 15, 2021

@ccfs

Here is the today version of the French file, adapted according your remarks/comments: fr.xml-21.11.15.zip
I also uploaded the latest French .ods update. I marked by "211115" (today) my modifications: PLL-reviewed.ods

1- I reversed the French translation of 'Get icons' to 'Get %s', as I had forseen it. You show me the other "sharing" of this value and you are right. The developer must create a new separate keyword to solve this issue.

2- About the "List" problem : I also adapted the translation, minimizing - but not solving - the French ambiguity.
ListeVSPrésentation 3

By the way, I noticed that there are already 2 lines to translate "List": #37 and #185.
Line #37 is the right one for the "header panel" ("Liste des fichiers" in French - arrow 1 - which should be "Présentation des fichiers" or "Style d'affichage inventaire" or ...) and line #185 is the exact meaning of the display options (the right panel) : there "Liste" is exactly part of the other display options (Details, etc.).
If Gaku identifies separately the two lines (f.i., line 37 -> ListTitle ??), the bug would be solved.

The current French language .xml joined is the best we can get with the current TE64 coding ;o))

Best regards
Pierre

@ccfs
Copy link

ccfs commented Nov 16, 2021

@Lidgeu,

TE translation process is basically a simple "text substition". It cannot do a different substitution according to where a caption appears. The only way to translate the 2 "List" above differently is to enhance TE to re-phrase one of them, and each translator provides a corresponding translation through a language file.

"Duplicated", "Same translation" and "XML" columns of the ODS file are filled with formula to provide data based on the input to "Translation" column. However they become actual values in the ODS file you posted above. Did you get a problem when you open the file at you side (by Microsoft Excel, I guess)?

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Nov 16, 2021 via email •
edited
Loading

@ccfs
Copy link

ccfs commented Nov 29, 2021

@Lidgeu,

I have updated the spreadsheet for recent TE changes and saved it in Excel format. Please let me know if there is any problem when you open the file.

LibreOffice cannot convert any user-defined function (macro) to Excel format. So I include that in a separate text file. You have to manually put it into the Excel file and do some minor adjustments so that the XML column can work.

Use the Excel file if you feel comfortable, or else use your own way to make up your language file.

fr_pl.zip

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Dec 1, 2021 via email

@ccfs
Copy link

ccfs commented Dec 2, 2021

I have just converted the XLSM file back to ODS. I suggest to work on this latest ODS file because it is based on TE 21.11.26 and includes a lot of changes recently.

The extra "fr" sheet is for information only. It shows you which captions in your fr.xml file have been removed from TE.

Since a lot of captions are vague, over-simplified or even misleading, you may need to try out a feature to understand what a caption actually means. This will probably cost you a few MONTHS to correctly translate all. Therefore I suggest to work on TE core, then the default add-ons, then the add-ons you use, then the add-ons you may use later, and lastly the remainings.

You can refer to TE Add-ons in Categories PDF for brief descriptions of most add-ons.

Sorry again I cannot find any attachment. Anyway, I don't know French. I cannot judge your translation. It is good as long as you feel acceptable.

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Dec 2, 2021

I have just downloaded the TE 21.11.26 ODS file and get the macros running ;o).
Many thanks for the TE Add-ons.in.Categories : these detailed description will be very helpful to understand what's going on.

Now I feel to be on the right track :o)
Let's work !!
In the mean time, here is the November, 30 version of the fr.xml, superseeding all the previous ones --> fr.xml-21.11.30.zip
It is worth to already insert it in the TE download package, to let the French users to take profit from these enhancements.

MORE TO COME ...

@ccfs
Copy link

ccfs commented Dec 3, 2021 •
edited
Loading

I had a glance of the language file and found:

	<text s="L">G</text>
	<text s="R">D</text>
	<text s="U">H</text>
	<text s="D">B</text>

Each of the four English letters has space character surrounded in the ODS. They should not be removed. Anyway, here is how I "translate". This is just for your reference. You decide to follow or not.

	<text s=" L ">←</text>
	<text s=" R ">→</text>
	<text s=" U ">↑</text>
	<text s=" D ">↓</text>

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Dec 5, 2021

Based on your last version of the ODS file, I was able to :

1- Fully complete the missing translatations (including the LRUD spaces). Here is the updated "French" ODS -> fr_pl-211205.ods
2- Rebuild a brand new "full" (i.e., containing all the add-ons translation included in ODS) fr.xml file. I left the blank lines to exactly match with the ODS column. Here is it -> fr.xml-full_211205.zip
3- Validate all the Kernel" TE and the add-ons I'm using (remarks, warnings, suggestions are welcome),
4- During the validation (made with 211205 TE prerelease), I encountered some problems. I summarized them here -> Translation Issues.pdf
5- I'll keep continuing to validate for other add-ons (installation for test needed), but from now the above loaded fr.xml zip IS the French current version to insert in the package delivery.

;o))

PS : For the (potential) translators unable to use an .ods file, why not to let them work on an English (common language for them) "Master" file like this one, generated from your ODS, same way of the French xml one. Should be more "appealing"
and comfortable for them to maintain.;o) -> EnglishMasterODS.zip

@ccfs
Copy link

ccfs commented Dec 7, 2021

  • fr_pl-211205.ods

3 pairs get "Same translation" TRUE. The second one of each pair will be dropped by TE silently.
"Everything" is also a product name. You probably do not need to translate it.

  • Translation Issues.pdf

1 Translation location not found
TE reuses the pop-up window of "View > Choose Details" of Windows Explorer. Therefore it is in the language of your system (French) and cannot be switched. Many parts of TE also work as such, e.g. context menu, File/Edit/View menus.

2 and 3
@tablacus, you scrambles some translated and not-translated words and parenthesis together into a caption, which is incorrect or strange in a foreign language (and in English too). Such caption should be changed to a single phrase in English so that it can be translated through a line in a language file.

20211207_103141
20211207_094024
20211207_094855
20211207_095450
20211207_095735

Regards,

@Lidgeu
Copy link
Author

Lidgeu commented Dec 7, 2021

  • fr_pl-211205.ods

3 pairs get "Same translation" TRUE. The second one of each pair will be dropped by TE silently. "Everything" is also a product name. You probably do not need to translate it.

  • Translation Issues.pdf

1 Translation location not found TE reuses the pop-up window of "View > Choose Details" of Windows Explorer. Therefore it is in the language of your system (French) and cannot be switched. Many parts of TE also work as such, e.g. context menu, File/Edit/View menus.
...

  1. I understand the useful duplicate "Same translation" process ;o). However, Your're right to be careful with that function.
    For example, in French "Edit" may be translated by "Edition" (which is the action name) OR "Editer" (which is the verb of the action to do) OR "Editez" (which is imperative, a request (injunction) to do something). Same for filter, a.s.o.
    As you know, a right translation depends on the context ... and the developer purpose. It's one of the reasons a good translator needs to validate "on site" (I mean during a real application execution) ;o)

  2. To me, "Everything" is not a "product name. Literally translated, "Every thing" means "Chaque chose --> Tout".
    So we will let 'as is'.

  3. "Translation not found". You are right !! You let me discover a stupid parameter of Windows 7 :o)).
    When you check on "NomDossier", the Windows Explorer just displays the folder parent 8-), completely useless !!

I hope Gaku will adapt according your suggestions.

Best regards

Pierre

@ccfs
Copy link

ccfs commented Feb 27, 2022

French ODS based on TE 22.2.23 to be updated
changes in some descriptions

@Lidgeu
Copy link
Author

Lidgeu commented Feb 28, 2022

Done ;o)
fr.22.2.23.updated.ods
fr.xml-22.2.23.zip
Question @ccfs : Is there an recent update of "TE.Add-ons.in.Categories.pdf" ? If yes, where can I download it ? ;o)

@ccfs
Copy link

ccfs commented Mar 1, 2022

the PDF has been updated.

@Lidgeu
Copy link
Author

Lidgeu commented Mar 1, 2022 via email

@ccfs
Copy link

ccfs commented Mar 29, 2022

French ODS based on TE 22.3.27 to be updated
new add-on "Quick notes"

@ccfs
Copy link

ccfs commented Apr 9, 2022

French ODS based on TE 22.3.27 to be updated (2022/4/9)
new add-ons

@Lidgeu
Copy link
Author

Lidgeu commented Apr 9, 2022

Done. "Quick notes" and "Layout" add-ons added ;o)

@ccfs
Copy link

ccfs commented May 25, 2022

French ODS based on TE 22.5.20 to be updated
new add-on "Show hash"

@Lidgeu
Copy link
Author

Lidgeu commented May 26, 2022

Done. "Show hash" and "Layout details" added. ;o)

@Lidgeu
Copy link
Author

Lidgeu commented Jul 10, 2022

@tablacus @ccfs
Hello,
Where the hell is this "blank" coming from ? (For getting a full clean French localization -true for any non English language)
BlankNotTranslated

Note : "aboutblank" addon is active ;o)

@ccfs
Copy link

ccfs commented Jul 12, 2022

TE has a few special "about:something" addresses. I do not find any way to translate that something.

@Lidgeu
Copy link
Author

Lidgeu commented Jul 12, 2022 via email

@Lidgeu
Copy link
Author

Lidgeu commented Jul 14, 2022 via email

@ccfs
Copy link

ccfs commented Jan 14, 2023

French ODS for TE 23.1.12 to be updated

  • new add-on "Split12"
  • new placeholder "Number or %" (Side tree view / Favorites bar)

@Lidgeu
Copy link
Author

Lidgeu commented Jan 14, 2023 via email

@Lidgeu
Copy link
Author

Lidgeu commented Jan 16, 2023

Here is the update :

FYI, I also completed and updated (Previous partial French translation spellcheck & corrections) of this add-on :

;o)

@ccfs
Copy link

ccfs commented Feb 2, 2023

French ODS for TE 23.1.31 to be updated
2 new add-ons:
Go home automatically
Color label sort

@Lidgeu
Copy link
Author

Lidgeu commented Feb 4, 2023

Here you are, Sir ;o)

By the way, one question : where can I found a tutorial to use "innersyncselect" addon?? :o))

@ccfs ccfs mentioned this issue Aug 1, 2023
Closed
@ccfs
Copy link

ccfs commented Jan 7, 2024

fr 24.1.7 to be updated.ods
new add-on: mpv

@Lidgeu
Copy link
Author

Lidgeu commented Jan 12, 2024 via email

@ccfs ccfs mentioned this issue Feb 16, 2024
Open
@ccfs
Copy link

ccfs commented Feb 16, 2024

The "blank" problem above has been solved with the patch.

@Lidgeu
Copy link
Author

Lidgeu commented Dec 29, 2024 via email

@ccfs
Copy link

ccfs commented Dec 30, 2024 •
edited
Loading

Please update this ODS to produce your language file. I have temporarily put a $ sign at where you will have to update.

@Lidgeu
Copy link
Author

Lidgeu commented Dec 30, 2024 via email

@ccfs
Copy link

ccfs commented Dec 31, 2024

May I suggest you to reply thru GitHub. Any attachment is lost if you reply thru email.

@Lidgeu
Copy link
Author

Lidgeu commented Jan 1, 2025

Sorry,

Here is the attachment of the French update
fr.24.12.23.updated.ods

@ccfs
Copy link

ccfs commented Jan 1, 2025

The "auto-correct" feature of LibreOffice changes straight quotation marks (as typed on keyboard) to curly quotation marks. For consistency, I have manually reverted them in the updated ODS and generated the XML file.
fr.24.12.23.updated.2.ods
fr_lidgeu 250101.zip

@Lidgeu
Copy link
Author

Lidgeu commented Jan 1, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tablacus @ccfs @Lidgeu