Week 0: Setting up KDE Builder

Thursday, 22 January 2026  |  Tanish Kumar

While the official coding period for SoK starts on January 23rd, my mentor, Finley Watson, kicked off a "preparation phase" this week to ensure we are ready to hit the ground running. I'm calling this "Week 0."

The goal was simple: set up kde-builder on my Fedora and compile Lokalize before the real work begins.

The Setup Struggle

I initially planned to use a manual build, but the Week 1 preparation guide provided by Finley explicitly recommended setting up kde-builder.

Of course, it didn't work on the first try. I kept hitting a Python error about a missing setproctitle module even though I had installed it.

After some digging, I realized my terminal path was missing ~/.local/bin, so the helper scripts weren't actually running. A quick fix to my .bashrc and a manual run of initial_setup.sh, and the build finally started.

Twenty minutes of compiling later, I had a working Lokalize built from source!

Since the build was working, I decided to take a peek at the bug I'm supposed to fix next week: the "Jumping Project Menu."

Basically, when you open a file, the Project menu physically shifts to the right. It's super annoying for muscle memory.

I dug into the .rc files (the XML that defines the UI) and found the culprit in lokalizemainwindowui.rc.

<MenuBar>
  <Menu name="file"><text>&amp;File</text>
    ...
  </Menu>

  <Merge/>  
  <Menu name="project"><text>&amp;Project</text>
    ...
  </Menu>

That tag tells KDE: "If a child window has extra menus, put them HERE."

When the Editor loads, it creates its own menus (like "Go" and "Edit"). Because of that tag, they get inserted right before the Project menu, pushing it down the line.

The Fix? I think I just need to "reserve the seats" in the main XML file. If I add placeholders for Edit, View, and Go in the main window, the Editor should merge into them instead of pushing everything else around.

I'll test that theory properly next week. For now, the environment is ready.

Image