KitwareMedical / KitwareMedical/SlicerCustomAppTemplate

After customizing one's own software using SlicerCustomAppTemplate, the original 3DSlicer translation file does not work

Open
#115 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
71
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Following the tutorial, I used SlicerCustomAppTemplate to generate custom software. After compilation
1. I used the installation translation process of the original version 3DSicer5.6.0 for translation, as shown in the figure, which can take effect

Image

2. I copied the path of the translation file to the new custom software bin directory, but the software cannot respond to the original translation

Image

Image

I'm not sure if it's due to a change in software name causing translation failure or some other reason. Is this a problem? I am looking forward to finding a solution, thank you.
Customized version: 3DSlicense 5.6.0
translation file:
[translations.zip](https://github.com/user-attachments/files/24929279/translations.zip)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the translation workflow described for SlicerCustomAppTemplate with the attached translations.zip and compare it with the original 3D Slicer 5.6.0 installation process. Investigate whether the custom software name or another packaging difference prevents the translation file from being discovered. Done means identifying the cause and documenting or verifying a working translation workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
internationalization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.