Hi, I’m Norwegian and use ÆØÅ in my alphabet and when I use my app I upload words containing the letters ÆØÅ.
But those letters becomes questionmarks, and I’ve been trying to find a solution for that, cuz now my childrens(7and9) are going to use my app, and it’s hard for them to read the whole word with questionmarks in it.
Before Kodular I used Thunkable, and also there in the community a while back I tried to use the WEB Encode and Decode function, and I’ve also tried the Replace text segment block, but I don’t get it to work.
Are there anyone who have blocks to show how it works?
So, how to not let the letter “ø” become a questionmark, any idea?
FYI: The letters ÆØÅ is displaying perfect when downloading if I change the letters directly inside Airtable cells. So if I put the word “Lønn” inside a cell manually it also displays “Lønn” when Getting the data. So it’s the upload function that destroys the letter somehow.
I don’t change anything, and it should work by replacing the text when uploading and again replace back when getting the data from airtable, but I havn’t got it to work
Don’t know why it does not work directly with a Global Variable, maybe someone else have an answer to that
Well, ty all for the tips
FYI: I don’t know why my previous post was flagged as all I said was I’ve been searching the forum both here and in Thunkable community for hours, and in return I get the comment “Search forum first”. I don’t see anything wrong with that
If I’m trying to develop new things into my app that I have not done before I always tries first, search forums and tries my best to figure out on my own before posting topics. But I’ve seen it’s become a trend to comment “Search forum first” on topics, so I guess it’s a new thing to do?
I know they are expensive operations, but not too much to be unusable in case of SHA1. Fireproofing a small string takes ~25ms on my device.
@Choofa Glad to hear that you got it working! I myself use the procedure with Firebase (hence the name). I store values in fireproof("tagName"), and fetch with that. To show tagName on the screen, I use antifire (otherwise the hashes would be shown onscreen). The upcasing and hashing makes the procedure foolproof.