Open eldcn opened 1 month ago
Currently we are defining string resource in .kt files which makes it hard to handle localization
.kt
values/strings.xml
Show Context Actions
Extract string resource
No response
Would be great; localization is up on the agenda after the cross-institution launch. We should ensure that we have the bits and pieces in place for that.
Problem
Currently we are defining string resource in
.kt
files which makes it hard to handle localizationSolution
values/strings.xml
of either app or the module owning the resourceShow Context Actions
>Extract string resource
Additional context
No response
Code of Conduct