You've got strange characters like "�" or "ö" display in your application? Yes, handling non-English characters in application code, files and databases can be a challenge, to say the least. Whether that's German Umlauts, Cyrillic letters, Asian Glyphs or Emojis: It's always a mess in an international application. In this session you will see why that is and how handling characters evolved in computing. You will also see how handling characters in applications and databases can be done less painfully. And don't worry when EBCDIC, BOM or ISO-8859-7 are Greek to you and your Unicode is a bit rusty: we'll have a look at them too!
Last active
June 24, 2016 05:55
-
-
Save heiglandreas/ffe508e6d1bd013b993a792c639e1294 to your computer and use it in GitHub Desktop.
'non-english' -> 'non-English'.
'persistent storage' -> could be jargon and put people off? Could simplify and say 'files and databases'.
'painfull' -> 'painfully' (the former is an adjective, the latter an adverb), or 'can be less painful' ('painfull' is also archaic, and 'painful' preferred).
Great! Just capitalize English. And you might want to work on the title :).
Add a bit about the target audience, especially the background or lack thereof that someone would need to get the most out of your talk :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
"painfull" should be "painfully." Otherwise, nice job. 😄