# ParaView translation discussion
**URL:** https://discourse.paraview.org/t/paraview-translation-discussion/2223
**Category:** Development
**Created:** [July 15, 2019, 5:21pm UTC](https://discourse.paraview.org/t/paraview-translation-discussion/2223 "2019-07-15T17:21:48Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 15, 2019, 5:21pm UTC](https://discourse.paraview.org/t/paraview-translation-discussion/2223/1 "2019-07-15T17:21:48Z")
**Is there interest into improving the support for translation in ParaView ?**
I’m currently adding a support for translation in a ParaView based app and there is a **lot** of non `tr()` visible QString in ParaView.
Some doc for these that do not know this :
[https://doc.qt.io/qt-5/linguist-manager.html](https://doc.qt.io/qt-5/linguist-manager.html)
If we consider that ParaView is “translatable” with some effort, we may need to take a few steps :
1. Do a general pass to add a many tr() as possible in ParaView
2. During the review process, check that visible string are tr()ed
3. Qt provide a tool to generate a translation file from .cxx and .ui files (lupdate). We may want to provide a tool to do the same from a servermanager xml file.
4. Something more advanced not yet designed ?
_As a side note, I have a question for those that have already experience with this mechanism._
_the translation file .ts provide translation by context. eg: in pqMyClass, “foo” is translated “bar” by calling `pqMyClass::tr("foo")`. Is there a way to specify a generic context to fallback on ? that would avoid duplicating translation. Unless we try to use QObject::tr() instead of pqMyClass::tr() in general._
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 16, 2019, 4:31am UTC](https://discourse.paraview.org/t/paraview-translation-discussion/2223/2 "2019-07-16T04:31:28Z")
I am supportive of increasing support for multiple languages in ParaView, but ignorant as to how it should be done.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 19, 2019, 3:59am UTC](https://discourse.paraview.org/t/paraview-translation-discussion/2223/3 "2019-09-19T03:59:40Z")
Sadly this will not go forward atm.
Closed MR for reference : [https://gitlab.kitware.com/paraview/paraview/merge\_requests/3407](https://gitlab.kitware.com/paraview/paraview/merge_requests/3407)
This will require a lot of work to do right. I think a prototype could be set up in a few days of works but it will contains still a lot of non translated strings. The prototype could be done in a language of one of the devs where he/she could translate the strings roughly.
---
### Author:  [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [March 18, 2021, 1:34am UTC](https://discourse.paraview.org/t/paraview-translation-discussion/2223/4 "2021-03-18T01:34:10Z")
Once the unicode compliance is complete in Paraview internationalization seems like the next logical step. Why can it not be done incrementally, as the closed MR demonstrated?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 18, 2021, 8:01am UTC](https://discourse.paraview.org/t/paraview-translation-discussion/2223/5 "2021-03-18T08:01:41Z")
Tbh it could be done incrementally, but the way to a fully translated ParaView will be long. Feel free to take over the MR.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 22, 2024, 7:43am UTC](https://discourse.paraview.org/t/paraview-translation-discussion/2223/6 "2024-04-22T07:43:09Z")
three years later, it is implemented 🙂
Discourse anouncement: [Help translate ParaView into your language!](https://discourse.paraview.org/t/help-translate-paraview-into-your-language/12467)
Blog: [https://www.kitware.com/help-translate-paraview-into-your-language/](https://www.kitware.com/help-translate-paraview-into-your-language/)