You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the localization of the app(s) and the web viewer planned? We could contribute a German localization, if there is any mechanism for that planned. This would involve all labels in the graphical interfaces but also the data entered for the points of interest could need to support several languages. The name of a building or even a room may be different in other languages.
The text was updated successfully, but these errors were encountered:
Localization is an interesting direction and we are sure that many other people will be interested in this.
There seem to be 2 directions:
a) Localizing the GUI language (e.g., through a settings option). This would relate to all different components: Viewer, Android, Windows, Architect, upcoming iOS. This will probably take more time, thus can remain here for the future releases.
b) Providing multi-lingual POI information: relates more to the Architect / API / backend. We should plan to offer this in the upcoming releases.
Dimitris (@dvaler01) can you please note (b) down to offer the localization mechanism in the next release of Viewer/Architect/API. It should then be easy to allow extending Windows, Android respectively.
Is the localization of the app(s) and the web viewer planned? We could contribute a German localization, if there is any mechanism for that planned. This would involve all labels in the graphical interfaces but also the data entered for the points of interest could need to support several languages. The name of a building or even a room may be different in other languages.
The text was updated successfully, but these errors were encountered: