QtCS25 - State and Direction of Qt's i18n and l10n framework: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
==Session Summary==
==Session Summary==


''Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.''
Session took place in the common area. The presentation was already done during the lightning talks.  
==Session Owners==
==Session Owners==


''Lorem Ipsum''
Masoud Jami


''Consetetur Sadipscing''
Jörg Bornemann


==Notes==
==Notes==
''Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.''
Talked to Vladimir who could give some more insights why id-based translations are preferred by some customers:
 
* translations can be re-used in completely separate parts of the project
* developers might not be fluent in English, separation between source code and displayed text is important
* id naming: some people create a tree-like hierarchy of objects and reflect them in string IDs


[[Category:QtCS2025]]
[[Category:QtCS2025]]

Revision as of 14:41, 8 May 2025

Session Summary

Session took place in the common area. The presentation was already done during the lightning talks.

Session Owners

Masoud Jami

Jörg Bornemann

Notes

Talked to Vladimir who could give some more insights why id-based translations are preferred by some customers:

  • translations can be re-used in completely separate parts of the project
  • developers might not be fluent in English, separation between source code and displayed text is important
  • id naming: some people create a tree-like hierarchy of objects and reflect them in string IDs