https://bugs.kde.org/show_bug.cgi?id=512748

surcouf <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #12 from surcouf <[email protected]> ---
Hello,
Regarding your point:
>     I'm looking for a way to install it since I do not find any .po files in 
> the debian kmymoney packages to overwrite them :)

If you have installed KMyMoney using your distribution's packages, then you
could overwrite your local translation file. The .po file you have from Xavier
Besnard must be transformed into .mo file. I suggest to look at this: :
https://community.kde.org/KDE_Localization/fr/applications#Tester_localement_le_fichier_traduit
to see how to transform it.

If you have installed KMyMoney using AppImage, then the .po file cannot help
you since the AppImage is a kind of black box for the end user. BUT there is a
solution: download a more recent AppImage file. They are available here:
https://kmymoney.org/appimage.html.
Then you may already have the "corrected" (regarding the translation issue of
this bug), or not. It depends on when the needed steps happened:
1- Xavier Besnard committed the corrected language file two days ago, 
2- According to Gitlab (see On
https://invent.kde.org/office/kmymoney/-/commits/5.2?ref_type=heads the commits
named "GIT_SILENT Sync po/docbooks with svn"), the language files have been
integrated this morning into the software
3- For example the last stable (=branch 5.2) AppImage file available is        
kmymoney-5.2-5001-linux-gcc-x86_64.AppImage     2025-11-30 14:22        150M   
 , which is from yesterday afternoon. So i presume it has not the most recent
language file correction yet. 

If you watch the webpage
https://cdn.kde.org/ci-builds/office/kmymoney/5.2/linux/ the next days, you may
find a newer version than today and it should contain the corrected language
file.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to