Bug 508048

hi Pieter.  this is strange, we just ship the kde and plasma defaults.  which branch did your translation work for plasma go into? master or Plasma/6.4 ??

I checked...

Could this be an answer to your question?

"The translation was done on "KF6-based stable" as can been found on:  https://l10n.kde.org/stats/gui/stable-kf6/team/nl/"

Please let me know if this is not the case...

(In reply to PK from comment #2)
> I checked...
> 
> Could this be an answer to your question?
> 
> "The translation was done on "KF6-based stable" as can been found on: 
> https://l10n.kde.org/stats/gui/stable-kf6/team/nl/"
> 
> Please let me know if this is not the case...

which packages in particular??

It were these packages:

discover._json_.po
kcm_touchpad.po
plasma-discover.po
libdiscover.po
kcm_about-distro.po
kcm_kscreen.po

(In reply to PK from comment #4)
> It were these packages:
> 
> discover._json_.po
> kcm_touchpad.po
> plasma-discover.po
> libdiscover.po
> kcm_about-distro.po
> kcm_kscreen.po

thanks for the added info.  using kinfocenter as an example, nl po for kcm_about_distro hasn't received any new translations since 3 months ago - https://invent.kde.org/plasma/kinfocenter/-/tree/Plasma/6.4/po/nl?ref_type=heads
whilst on master changes were synced in 3 weeks ago.  
if you are positive your changes/commits were to stable-kf6 and not trunk-kf6 then something is amiss with scripty and the po syncing

I just conducted a little experiment...

I copied the entire content of the folder /trunk6/nl/messages/discover/ to another place. Then I executed a scrip on it to change the po-files to mo-files and copy them to the appropriate place of the system. (bottom of this comment)
Direct after that Discover was still using the old and (if I may say so) not so attractive, Dutch translations.

But then:
I did "svn up" and repeated the process. To my surprise Discover on my neon user edition was using the new translation!
So the trunk6 is updated on the kde-server. Only Neon doesn't seems to pick this changes up.
I hope this experiment helps to understand what's wrong...

script:
#!/bin/bash

#set -x -v

for i in ./*.po
do
  fn=`basename $i .po`
  msgfmt $fn.po -o $fn.mo
      # sudo apt install gettext
done
rm mo/*.mo
mkdir mo
mv *.mo mo
#
echo
#
    # mo bestanden naar de NL map?
        read -p ".mo bestanden uit de mo-map naar de NL-bestanden map kopieren? j/n " -n 1 -r
        echo    # (optional) move to a new line
        if [[ $REPLY =~ ^[YyJj]$ ]]
        then
            sudo cp mo/*.mo /usr/share/locale/nl/LC_MESSAGES/ 
        fi

currently trunk-kf6 svn refers to the plasma master branch (which will become plasma 6.5) .
stable-kf6 svn refers to the plasma 6.4 branch (presently released as 6.4.4 and which will next become plasma 6.4.5)
scripty is the i18n which runs nightly and syncs the relevant svn i18n branches to their matching application branch.
neon merely packages what is in the application branches after scripty has run every night.

Oh, that would be very valuable information!

Already in the time we had no upload rights we had to wait forever until our contributions were visible. This could very well explain that. It would be caused by the configuration we "inherited"...

I thank you very much for your answer...

(In reply to PK from comment #8)
> Oh, that would be very valuable information!
> 
> Already in the time we had no upload rights we had to wait forever until our
> contributions were visible. This could very well explain that. It would be
> caused by the configuration we "inherited"...
> 
> I thank you very much for your answer...
it just occurred to me to mention that if you run neon unstable in a vm it will already have the translations as it tracks the master branches of each product/app/framework/library ;)