yeah not sure that’s possible my friend because that value is what actually goes into different tables as a primary key of sorts. primary keys need to follow the same standard almost across all database engines with some minor exceptions that allow different characters to be used. to guarantee compatibility, it’s always best advised to use a consistent database friendly approach with your values.
imagine this, you have an app that has a list, but your app can appear in 5 different languages. which of of the values should we store in our database? lang1, 2, 3, or the base value that was set up against the list? each one of those values would require a column in order to save that in that language. that’s not entirely unfeasible, but probably not a great practice. in addition, using this approach allows you to be able to tell the different between a “No” for question1, and a “No” for question 2 that is if the database values have q1no and q2no instead of just a “no”. many things you can achieve with this especially if you’re using statistical analysis software and tools such as “R”.
my advice on this issue is to get all your list entries in an excel file somewhere, and perform a translation via a VLookup on excel. then use that output to report. that’s what we do when we need to display these values in a cosmetically appealing way.
Perhaps Dimagi has something that offers this functionality, and if not, maybe put it on our wishlist? I can certainly see it being heavily used