#3 French translation

[Rookiestyle]

Hi @fanchy,

thanks for creating a french translation and sorry to hear that you're facing issues with the translation not being used.

Please use the attached debug build of the plugin, place it in your KeePass plugin's folder and restart KeePass. When you close KeePass, it will ask you to open the debug file it created. Please attach this debug file as well as the translation file you created to this ticket.

[Anonymous]

Hi,

Thanks for your answer.

Some more explanations: first, I tried with the XML file UTF-8 encoded (in declaration and with file saving encoding).

Then, I looked at the German translation file that you provide (I was thinking that maybe the accents in my file would break the XML) and I saw this one was UTF-16 declared. So I retried with UTF-16 (declaration + file saving encoding) with no more success here.

Take a look at the 2 files provided with my current answer (there is the debug.xml file you asked). It says that there is an XML error.

I'm still thinking of accent breaking it but I don't know why (because I saw the german one with accents too - note that I didn't try it).

I'm waiting forward your hint or solution.

Hope the french translation will satisfy you.

Fanch

[Rookiestyle]

Thanks for your support!
I obviously messed up the encoding kentioned inside the template file and the encoding itself.

Please retry with the attached file, it works for me.
If this works for you, I'll upload it.

I will then also release a version 1.5.2 which is a bit more robust in handling translations

[Anonymous]

Re,

I didn't see your attachment file before so I though you'd reference to normal files downloading so I did it again and replace content text with my translation and it worked!

But I need some more informations because I want the translation to be precise and there are some stuffs I'm not sure to get:

• AskRecalcAll: is this for ALL entries or ALL SELECTED (because of the word "affected", I'm not sure what you mean here)?
• OptionsInactive: does this reset PEDcalc previously set for this entry?
• OptionsExpireNow: its name suggest to set this entry as expired now but its value suggest for several entries, which is a bit confusing. What does it do really?
• ErrorInitExpiryDate: what does the {0} stands for? Entry or date (which change the meaning in french)

Also, I can't find in the application where to find those translated string:
- InheritInherit
- InheritInactive
- NewExpiryDateTooltip

I want to be sure to get the context of them to ensure french translation is correct.

With your answers, I'll make a final version that I'll send you there and we'll be good for it.

:-)

Note: as I was searching in the application for PEDcalc text, I figured out that there wasn't PEDcalc option with the "KPEnhancedEntryView" (that allow fields edition in the preview panel). I don't know if it's on your side or the KPEnhancedEntryView's author but that would be great to retrieve it there too.

[Rookiestyle]

• AskRecalcAll will process all selected entries if you opened the PEDCalc form from the entry's context menu
• AskRecalcAll will process all entries in the selected group including its subgroups if you opened the PEDCalc form from a group's context menu - exception: groups and entries that do NOT inherit the setting are skipped
• OptionsInactive will deactivate PEDCalc for the affected entries which means: Expiry date will not be changed when changing the password
• OptionsExpireNow will flag all affected entries as expired
• ErrorInitExpiryDate - The {0} will be replaced by the expiry date that could not be set, e. g. 'could not be set to Friday, Feb 14 2020'
• InheritInherit and InheritInactive will be shown in the o0tional column that youmcan activate using View - Configure columns...
• NewExpiryDateTooltip: If you change the password in the entry form the new calculated expiry date will be shown underneath the standard field for the expiry date. This text will be shown as tooltip when hovering the new calculated expiry date

I'll try to integrate into KPEnhancedEntryView but I'm not sure whether it will work out.

[Anonymous]

Thanks for your answers, it's a lot clearer.

I updated the translation file consequently (that you can find in attachment of this message).

For the KPEnhancedEntryView interaction, that would be great but I understand that it's not only from your side. It was just for the info (and if it works, that would be really awesome).

Thanks for all your explanations and your time about it.

Good continuation with it.
Bye,
Fanch

[Rookiestyle]

I uploaded your translation and also released the beta version that you tested with as slightly improved official version.

I'll look into KPEEV integration but this might take some time.

Thanks again for contributing your translation!