In this meeting, the State Changers discuss the process of translating a web app and ensuring that the software recognizes the translation. A participant is in the process of translating an app into Spanish and has achieved this through WeWeb, a website builder. They discuss how internationalization is achieved through JavaScript and its functionality. Given that understanding the local computer's language setting enables the proper rendition of the app, it's important that the right message is sent to the 'back end', especially regarding the language preference.
There was also mention of the built-in internationalization system in WeWeb (referred to as 'I one 8 n') which identifies which language the user is currently in. There was a discussion about the challenges of getting fancy with languages and how layout implications come into play with languages that are read and written differently (i.e., Middle Eastern languages or East Asian text). It was concluded that it's crucial to figure out the specific languages needed before diving into complex translation jobs. In this case, the participant was primarily interested in Spanish translation. Overall, the aim is to be keenly aware of the user's language mode to make informed decisions beyond ordinary text. No specific tools or technologies, such as "Xano", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", or "AI21", were specifically mentioned in this meeting.
(Source: State Change Office Hours 9/21/2023 )
