Reply To: antiX23-desktop-files: Resource at Transifex has been updated.

Forum › Forums › antiX-development › Translations › antiX23-desktop-files: Resource at Transifex has been updated. › Reply To: antiX23-desktop-files: Resource at Transifex has been updated.

#202114
Wallon
Member

    Bug: XML menu generation failure on JWM due to unescaped “&” in .desktop files

    I am using antiX and I encountered a recurring issue where the menu system fails to generate correctly when using JWM (Joe’s Window Manager).

    The problem is that several .desktop files in /usr/local/lib/antiX/antix26-desktop-files/reservoir/ contain the “&” character in their Name or GenericName fields.

    Because JWM’s menu generator relies on XML, the raw & character causes it to crash.

    I verified this by running jwm -p (the JWM configuration validator), which reports the following error:

    JWM: warning: $HOME/.jwm/menu-applications[54]: invalid entity: “& Equali”

    In the file /home/wallon/.jwm/menu-applications, you have this;

    
    <Program label="Audio Effects & Equaliser (“EasyEffects”)" icon="/usr/share/icons/Qogir/scalable/apps/com.github.wwmm.easyeffects.png">easyeffects</Program>
    

    These characters should be properly escaped as "&" to ensure compatibility.

    I identified the following files as affected:

    antiX-docs.desktop

    antiX-hostname-changer.desktop

    antiX-memory-manager.desktop

    antix-pdm.desktop

    app-select.desktop

    barrier.desktop

    com.github.wwmm.easyeffects.desktop

    ft10-setup.desktop

    iDevice-Mounter.desktop

    luckybackup.desktop

    luckybackup-gnome-su.desktop

    set_time-and_date.desktop

    Could you please update these files to use "&" instead of &?

    This would fix the menu generation issue for JWM users.

    Thank you in advance for your support.

    PS : « I tried to write & but the forum automatically converts it back to &, which exactly illustrates why the JWM menu generator fails on these files! »

    “I suggest replacing the raw ampersand character with the corresponding XML entity. In technical terms, it should be the ampersand symbol followed by the letters ‘amp’ and a semicolon.”

    • This reply was modified 5 months, 1 week ago by Wallon.
    • This reply was modified 5 months, 1 week ago by Wallon.
    • This reply was modified 5 months, 1 week ago by Wallon.