search

CR6Community / CR-6-touchscreen

CR-6 SE touchscreen software extended with more functionality and pages than the stock CR-6 touchscreen software.
https://cr6community-support-team.gitbook.io/cr6comm-touchscreen-refactored-firmware-docs/
152 stars 34 forks source link

Question/Offer: contribute translation #16

Closed rmeissn closed 3 years ago

rmeissn commented 3 years ago

I'd like to contribute a german translation for the touchscreen menus. Is there something like a guide on how to do this?

Sebazzz commented 3 years ago

Internationalization support in DGUS DWIN is very cumbersome and not feasible. The background images of each page has the text hardcoded. To translate and have it first-class, you would need to duplicate all the bmps, give it a separate ID, and maintain that mapping in firmware as well.

So, what I would suggest you do:

  1. Fork this repository.
  2. Work on the extui branch (this is the branch for all work going forward)
  3. In your fork, follow the steps in the README.md to change the current bitmaps and translate them. @Nushio has made XCF files as the source of these bitmaps, usable in Gimp, to make life easier but you can follow your own way of course.
  4. When we change something, it is up to you to replicate those screen changes. Therefore I recommend only to update the screen backgrounds and don't use the DWIN editor other for the purpose of generating the ICL.
  5. German touch screen builds are up to you to provide which would then need to be made from the same moment as we are releasing builds.

Good luck, and if you have any questions feel free to use this issue for it. You can also drop by in our Discord.

rmeissn commented 3 years ago

FYI: Creality released a new Firmware today (v2.0.1.2), which offers various languages for the touchscreen. They didn't hardcode these to the images, so it must be somewhere within the firmware. Unfortunately they haven't released the sources yet (I think).

Sebazzz commented 3 years ago

They hardcoded this in the DWIN icon files (ICL) - this would require maintaining a mapping in firmware. This is not feasible, especially not for the few working on this firmware. We would also need to replicate (=reimplement) the changes.

Because of this, it is best if someone wants to have a language, that person maintains his own set of background images and distributes that.