7 ms·
Your language sucks
- krispyfi 12y agoI don't see anything here that hasn't been solved by ICU. Am I missing something? http://site.icu-project.org/ http://site.icu-project.org/ Anecdote time: I once worked on a software project where all of the sorting was done using an internal library made by a Large Trustworthy International Corporation. We discovered halfway through that the transitive property was not being maintained during sorts mixing half-width and full-width numerals. (In other words, 1 < 2 < 1 > 1.) Switching to ICU left me ultra-impressed at its thoroughness.
- Someone 12y agoICU is very good, but even it isn't perfect, and they know it. http://userguide.icu-project.org/collation/customization http://userguide.icu-project.org/collation/customization: "ICU provides a data-driven, flexible, and run-time-customizable mechanism called "tailoring". Tailoring overrides the default order of code points and the values of the ICU Collation Service attributes" Also, you sometimes need context to properly sort strings. Examples: Are you sorting phone book entries or items in a dictionary? In some languages, that does make a difference. Are you sorting Swiss German or German German? Given two 'obviously' Italian words, should you apply Italian collation rules? You probably/maybe shouldn't when both are words in an English-language dictionary. Some library catalogs want(ed?) to sort "2001: a Space Odyssey" as "Two thousand and…" (http://en.m.wikipedia.org/wiki/Library_catalog#Sorting http://en.m.wikipedia.org/wiki/Library_catalog#Sorting) For the latter, even that ICU feature to customize sorting won't help you.
- notacoward 12y agoWhether you agree with its tone/conclusion or not, this is a really informative compilation of problems that can arise in processing international text. Very nice.
- m_mueller 12y agoI think the tone is intentionally aggressive - it drives clicks and spices things up - I was at least entertained.
- packetized 12y agoThe points made may be salient, but the tone is so condescending as to be nearly unreadable without getting angry. A large number of his points around languages that are radically different from English could be summed up as: "Your language sucks to deal with in computing because your native country didn't develop computing machinery first." This fairly reeks of tone-deafness.
- jypie 12y agoThis. I was thinking the same.
- archagon 12y agoOn one hand, I realize it's totally meant tongue-in-cheek. So I don't want to pick on the article, because it's useful and funny. On the other hand, I've been seeing this attitude in regards to other topics lately. "Why can't humans be perfect... like this machine?" Well, guess what, bub. We came first, and this stupid computer had better get used to it. Me, I like my clumsy, imperfect analog world.
- cbd1984 12y ago"That's nice. I'll deal with it when you make it economically worthwhile for me to deal with it. Until then, enjoy your fixed-format fields that truncate your name." Sincerely, Christophe
- dotfish 12y agoReally? It just sounds condescending and arrogant in a very Anglo-centric way even if I try to read the satire between the lines. If that was the intention, the author isn't very good at it.
- robzyb 12y agoThe author is someone who is trying to apply a simple and consistent set of rules to non-perfect systems. The author of course gets 'angry' with the super-non-perfect systems. Those languages are very difficult to deal with, and he is expressing his frustration. That doesn't mean he's being condescending nor arrogant.
- Argorak 12y agoAll I hear is: "I wanted to model the real world and it didn't fit my mental model." Sadly, there is some information in all that cruft that is interesting to people coming from an english context when dealing with international character handling, but well, nothing you couldn't get somewhere else.
- oranguntan 12y agoTurns out nerds are actually not necessarily as godly intelligent as they base their identities around being, and are actually pretty bigoted a lot of the time
- mahkoh 12y agoFunny, but ss and ß are not equivalent, e.g., "Busse" != "Buße".
- beefhash 12y agoDepends, actually. In Switzerland, you do write "Buße" as "Busse", despite the different pronounciation indicated with ß. The German written in Switzerland just doesn't know the ß character and uses "ss". Nonetheless, you're right if you're just looking at German as written and used in Germany (And maybe Austria? Not sure how they handle ß there).
- collyw 12y agoNot the best source of information, but Yahoo answers would say otherwise: https://answers.yahoo.com/question/index?qid=20070715142605AAHjJYt https://answers.yahoo.com/question/index?qid=20070715142605A...
- rowyourboat 12y agoYahoo Answers is correct for Switzerland, wrong for Germany and Austria, and wrong for historical uses of ß.
- glandium 12y agoThe worst part is that he's just talking about things like collation, that are relevant to the libc API. Add displaying that text to the equation and the list explodes.
- bottled_poe 12y agoThese are human languages created and used by humans, they weren't planned, they just happened. They get used independently with loosely applied rules. I'm not really sure what the point of this article was. Was it to state that human language != programming language? Thanks for the revelation. I will surely stay posted to receive further brain-burstingly deep insights.
- Trufa 12y agoI think the point was just to show all the complications that can appear representing human language for a computer to understand. I don't think the author actually thinks that language suck, though I can't speak for him, he seems to be too knowledgeable on languages for not actually appreciating them.
- muyuu 12y agoYep, languages are not made to be easily encoded in binary form. Also, symbol systems are just tiny bits of what a human language really is. In regards to grammar/semantics and phonetics for example, English is painfully loose to deal with in a programmatic way. That's just the way things are. That said, I believe Unicode's approach to inclusion of new characters in the set is wrong. It shouldn't be so dynamic. Unicode needs a smaller base, a standard extension system and standard extensions (in a standard extension format, reviewed in long but predictable timeframes, lets say every 10 or 20 years). The current system is a pain.
- deleted 12y ago[deleted]
- jng 12y agoClearly tongue-in-cheek, and informative. So nice somehow. But still: the fact that English phonology and orthography are only lightly related, and hardly anyone is willing to do the effort to fix this, should give the author second thoughts on complaining about others' artifacts and not complaining about the ones in English. Many languages have pure or nearly-pure phonetic orthographies, which are a pleasure to use. English could have one. And as the de-facto international language, it would help make everyone's life better. And it just won't happen.
- sho_hn 12y ago> and informative. There's a lot of half-knowledge and misdirection in this blog post, though. * Languages aren't writing systems, and vice-versa. * There are often decent reasons and upsides to the things he calls out as sucking. His rant on Hangul, for example - for human users, the morpho-syllabic grouping of letters into blocks in Korean writing tends to be beneficial, because they make the orthography of morphemes in different contexts more regular and morpheme reuse smoother. I also tend to consider the way Hangul is implemented in Unicode actually quite clever (you can use a formula to map from the code points of the individual letters to the code points of the pre-composed blocks). (I've contrasted Chinese and Hangul a little in this LWN comment: http://lwn.net/Articles/608260/ http://lwn.net/Articles/608260/) * The German ß isn't a simple ligature for 'ss'. It has a different history, an orthographic dimension and also serves as a useful prounciation hint. * Point 5, "The width of a character depends on context", is full of half-knowledge. First of, it's not "Jamo vowel" - 자모 (ja-mo) is the Korean word for "letter", so it's "vowel jamo" if anything. The alphabet is called 한글 (han-gul). Second, combining characters aren't in any way unique to Asian scripts in Unicode. Unicode contains separate code points for the individual Hangul letters and the blocks they can be combined into. Unicode also contains separate code points for Latin letters and the various diacritics and accents they combine with in Latin-derived Western scripts, along with code points for those combinations. For human users, these sort of consistent combinatorics in a script are a boon, and that Unicode chooses to represent both primitive elements and combined versions is a general trait of Unicode. In general, the thrust here is "your writing systems sucks for me while doing my job", which is subject to this guy's performance and qualifications. It's not the same as "writing system sucks for its users". I find the specter of stuff like this catching on as memes among linguistically and culturally ignorant hackers (because hey, we write English, so we're in the doing-it-right camp, right?) frightening, because programmer convenience is only one factor among many, and most likely not the most important one.
- stannol 12y agoß is not equivalent to ss, that's just plain wrong. Simple example: "In Maßen" means "in moderation" while "In Massen" means "en masse".
- FeepingCreature 12y agoß is equivalent to ss for the purpose of determining alphabetic order, same as ä is equivalent to ae, etc.
- rndgermandude 12y agoActually, it's more messed up than this. In Germany, the DIN 5007 defines two variants: 1) ä and a are equivalent (normal order, e.g. in an encyclopedia) 2) ä and ae are equivalent (to be used in "name lists", e.g. telephone books) But Germany is not the only place where German is one of the official languages. E.g. there is an "Austrian order", where a is followed by ä, except for name lists where often DIN 5007 variant 2 is used as well (ä equivalent to ae). Then again, Swedish also knows the letter "ä", but there ä is (usually) sorted after z (well, after å which comes after z). Now, imagine you run an English-language service but need to sort surnames such as "Ährlich". What sort order would be the right one? DIN 5007/1, 5007/2, Austrian, Swedish, something else entirely? Imagine you run a German-language service that is frequented by Germans and Austrians...
- TillE 12y agoWell yes, because you're distinguishing between Masse and Maß (Mass). They're not precisely equivalent if you're attempting to determine meaning, but for many purposes they are. For example, searching for "ss" in Chrome will hit ß. That's good behavior.
- kazinator 12y agoDoesn't it depend on region? ISTR they don't use ß in Switzerland, so there is no Massen versus Maßen.
- 12y ago
- mpu 12y agoAnd you are a retarded narrow-minded programmer. Go speak json in your own fictive country. Or, just shut up and take these issues as challenges.
- jedanbik 12y agoYour colonial approach to understanding diverse forms of human to human communication sucks. Like seriously, ASCII is supposed to be global? Lazy at best.
- cwyers 12y ago"POSIX doesn't do Titlecase." So that's an example of why your language sucks, not why POSIX sucks? Sure thing, guy.
- deleted 12y ago[deleted]
- dsirijus 12y agoI'll do my best to fix my language as soon as you fix your units. Your units suck.
- alkonaut 12y agoLet's not forget the horrible mm/dd/yyyy format. I need y'all to just use U.S English combined with ISO dates and metric units. Thanks.
- dsirijus 12y agoSold. Now we just need to get 7.2 billion minus 2 people on-board.
- lucb1e 12y agoI think pretty much everyone here would agree. It's common convention that we need to change. I'm Dutch and trying to push for YYYY-MM-DD because it's the only format that makes sense when sorting. Classmates have a lot of trouble with it and still put "Notes 18-10.docx" in a directory full of "Notes 2014-10-18.odt"-like files. Though I would be pretty fine with DD-MM-YYYY, at least be consistent... The only format that I really object to is the American MM/DD/YYYY format.
- oftenwrong 12y agoDD-MM-YYYY -> "19th of October" MM/DD/YYYY -> "October 19th" Americans typically would say the latter, so it is consistent in that sense.
- alkonaut 12y agoSo the format comes from how it is read? That sounds plausible. "October 19th, 2014". I'd pronounce a date like "day, month, year" but always format it yyyy-mm-dd, it never struck me that a date format (abbreviation) should be possible to pronounce without first parsing it completely. It does make sense, I just never thought about it. A reasonable (i.e. sortable) date format is 2014/10/19 but that would make sense in spoken form only as "2014, October 19th" which doesn't sound quite right. A sidenote: in northern europe (Germany, Sweden etc.) we do it wrong on addresses: [Street, Number, PostalCode, City/Region, Country]. Going from smallest to largest context is actually done correctly in english [Number, Street, PostalCode, City/Region, Country]. You can sort addresses lexically!
- vesinisa 12y agoAs a Finnish speaker, I must disappoint you that both Russian and English do have broken alphabets (although this might not affect their character coding). English makes extensive use of silent letters and letters whose pronunciation is dependent on the context (word) they appear in (take e in "context" and "appear" as an out of hat example). I haven't studied much Russian, but I know that the letter ъ in their alphabet is never pronounced, and instead used to modify the pronunciation of the preceding letter.
- maximumoverload 12y agoThis article is speaking clearly from the encoding and sorting view, not the easiness to learn or the logic of pronounciation.
- arh68 12y agoEnglish pronunciation leads to algorithms like Soundex [1], which just wouldn't seem necessary if words were written purely phonetically. Hangul gets closer, in a way. It seems hard to make rhymes with words like 'reprise' and avoid 'despise'. Not all languages need to be so ambiguous. [1] https://en.wikipedia.org/wiki/Soundex https://en.wikipedia.org/wiki/Soundex
- lomnakkus 12y agoYou really don't want a writing system which is too tied to pronunciation. If you go too far in that direction you'll end up with people with different dialects of the same language not being able to communicate clearly, even in writing! That would be a very undesirable state of affairs. Yet you still want some correlation between spelling and pronunciation, otherwise the writing system essentially becomes completely arbitrary and thus impossible to learn (since we humans rely so much on pattern recognition for learning).
- efesak 12y agoI am from country with strongly phonetical language and you are just plainly wrong. There are minor dialects but it is considered rather as slang in compare to language taught in schools or comunicate with officials or even broader audience. (On the other side, it is much more difficult for us to learn English and get used to that disconection between alphabet and said words. And we don't have spelling competitions :).)
- snarfy 12y agoWe have lots of shitty representations. Try delving into DateTime sometime. Korean (Hangul) does not suck, btw. The languages have been around hundreds of years, how long has your machine representation been around? Give it time. It just shows the software is still immature relative to the problem.
- nnq 12y agoOP should be thankful to the Greek, Roman and Arab ancient civilizations for sane-to-compute-with languages. Basically all other languages are so fucked up and mind-fucking that it's no wonder modern mathematics, science, engineering and then computer science developed so fast in particular regions of the world... not to be a cultural bigot, but Sapir-Whorf ftw :)
- jeffreyrogers 12y agoSapir-Whorf is largely discredited in modern linguistics (especially so for the strong form that your comment seems to suggest). The general consensus is that human languages are more or less equivalent in their expressive power. (Note that doesn't mean certain writing systems aren't easier to learn/use than others. It's important to distinguish reading/writing from language).
- deleted 12y ago[deleted]
- mikedwebdev 12y agoI enjoyed the article and found it refreshing in this apocalyptic politically correct world.
- ddod 12y agoThis article is interesting in that, while it's not the intention of the writer, it seems to point out some technical underpinnings for how language might impact culture. If a computer's handling of a language can vary so drastically, imagine how the human brain must deal with expressing or receiving complex thoughts through these. I recall reading some discussion of this concept in the field of International Relations' Constructivist theory, but any salient links escape me now.
- ethanpoole 12y ago> If a computer's handling of a language can vary so drastically, imagine how the human brain must deal with expressing or receiving complex thoughts through these. Orthography and language are not the same thing. Having a complex orthography has no bearing on processing complexity. If a language has a complex orthography, it may be hard to read and write, which are learned skills, but it won't be hard to speak and listen (which are naturally acquired skills given exposure to a language in the critical period).
- ddod 12y agoThat assumes that each of these properties exist in a vacuum, which is surely not the case. There's an obvious interaction between written and spoken language, and even without that, hundreds or thousands of years of differences in the written interactions and data transferred through reading within a culture could have immense impact on collective experiences and ways of thinking.
- rowyourboat 12y agoEven if it's tongue-in-cheek, I take issue with the general sentiment. If supporting languages spoken in the real world sucks, then we need better approaches to dealing with text. Not more whining about how unicode is hard.
- ethanpoole 12y agoThese are all complaints about orthography, not language.
- deleted 12y ago[deleted]
- ernesth 12y ago16. Hyphenation in your language is context dependent. English, your rules for deciding how to hyphen words are JUST HORRIBLY BROKEN! Hyphenation should at most depend on the word to be hyphenated, not on the semantics of the whole sentence.
- bane 12y agoThis makes me wonder what effect printing had on English. English used to be chock full of ligatures and special forms for letters (s and ſ for example). I can only imagine as a typesetter and type maker this was all very annoying and people simply started to drop them. However, WP claims [1] ligatures made typesetting easier and it was the introduction of Sans serif fonts in the 20th century that finally drove them away. I'd be interested in a more definitive history. In either case, by the early 20th century, English (and most Latin based writing systems) were in pretty good shape for computerization, and the limited capacity of computing systems were kind of built around English orthography. Nevertheless, most of these complaints would be true of English as well if we had carried through with our traditional system of writing. One can almost think of Hangul as a 100% ligature based writing system...there's fairly complex rules about what letters can be typed next to what other letters and produce a valid character. In Asia, it took longer for general purpose computing to catch on because of both memory and high-resolution display requirements. 7-bit characters being displayed in an 8x8 on-screen block weren't going to cut it. It took several generations of advancement before computers that could handle general purpose Japanese properly went on sale. For Japan, a culture that prizes tradition in many ways, the idea of just throwing away 2 of the 3 written systems in order to cram writing into barely functional computing systems, and then adopting that convention culture wide, would be unthinkable. Japan instead went full-tilt on a paper-based system and computerization was focused on scanning and transmission: fax machines, scanners, high speed telecommunications, etc. Even today, the typical Japanese office is a paper-filled minefield full of paper handling devices the typical American office haven't seen since the early 1980s. More importantly, there are reasons the Japanese use three (really four if you count romaji) scripts. Something written in katakana gives it an elements of "foreignness", a bit of semantic hinting about it's origin and how it should be considered. Imagine you're 11 years old about to play the role of a Western Knight in a video game, the game asks you to input your name, but only offers you katakana, this feels to you more immersive. We have ways of trying to do the same in English, but it's far more limited. Before computing took off, handling Asian languages was always a chore. When telegraphs were common, Chinese was encoded using a complex telegraph code [2]. This code was so useful that it's still used today in some places. During the cultural revolution, China had a moment where they could have introduced a simpler orthography, Zhuyin Fuhao, that's easy to learn to read and write (only slightly more complicated than Korean) and has full tonal representation. But it does a poor job disambiguating the tremendous number of homophones in the highly monosyllabic dialects of Chinese. It also doesn't provide a unified representation for words across dialects (the names "Wu" and "Ng" might be the same Chinese characters, but would be written differently in Zhuyin Fuhao). This would reverse thousands of years of cultural unification via written scripts previously enjoyed by China's many ethnicities and dialect speakers. (Fun fact, Christianity was first spread to Korea through Korean diplomatic missions to China, where Korean scholars communicated with Chinese converts through writing only as they didn't speak each other's language). These tradeoffs were simply unacceptable and instead China simply tried to reduce the number of strokes and characters in their writing reform. So does all this suck for computing? Yeah sure. But there's lots of weight in the semantics providing the why things are the way they are. China can't just adopt a simple to compute writing system any more easily than English Speakers could adopt a complex logography. Or for English Speakers to adopt a sane spelling system (the reasons for why our spelling is so horrible are similar to many of the historic reasons Asian languages have hung on to their overly complex orthographies). If he's complaining about these things and pointing to English as an island of relative sanity, he should be glad he doesn't have to support older versions of the English language and orthography! HWÆT, WE GAR-DEna in geardagum, þeodcyninga þrym gefrunon, hu ða æþelingas ellen fremedon! 1 - https://en.wikipedia.org/wiki/Typographic_ligature https://en.wikipedia.org/wiki/Typographic_ligature 2 - https://en.wikipedia.org/wiki/Chinese_telegraph_code https://en.wikipedia.org/wiki/Chinese_telegraph_code
- eric_bullington 12y agoWell, this may be the first time anyone, anywhere called the Georgian language "straight-forward". Georgian is a very cool language with a fascinating alphabet, but it's almost mind-bendingly complex. Also, Russian, the other language listed in addition to English and Georgian as "not-broken", has many irregular noun declensions ("unstable" cases in the writer's unusual terminology), which was one of his indicators for "broken" languages. In fact, 99% of all languages with a noun case system have at least some irregular cases. I'd say 100%, but then I'm sure someone will point to some language spoken by 10 people in a remote village in the Caucasus mountains that features strictly regular noun declensions.
- Cyph0n 12y agoNo mention of Arabic anywhere. Has OP not worked with it? In any case, how easy/hard is it to work with in data processing?
- asveikau 12y agoThe article does mention RTL languages (Arabic, Hebrew, Farsi?) They are kind of annoying to deal with especially when you have multilingual text. (Google "Unicode bidi") And UIs have to be mirrored.
- osmala 12y agoYou can recognize a broken writing system truly from two hints. A) It takes several years to learn how to write for a native child. B) Or there is spelling competitions with native children.
- ClashTheBunny 12y agoEnglish still has a specific ligature that's treated specially if things are done by the book: "Mc". All Rolodex/card catalog systems included a special position for it and they were sorted separately.
- sssilver 12y agoAs an Armenian, I'm not sure I understand his point about the Armenian language. What does "case conversions which are not reversible" mean?
- waxjar 12y agoThis article could be summed up with "My tools are built with (primarily) english in mind and that's a problem for me when dealing with languages other than english".
- lambda 12y agoSo, this is actually more about "your writing system, and legacy encodings of it, suck." While we do still have to support legacy encodings, increasingly we should just be using a universal encoding that doesn't have all of these problems he mentions. UTF-8 is such an encoding; it is ASCII compatible, contains no nulls, has the usual ASCII control characters encoded the same, no shift sequences, if you jump to an arbitrary byte in the middle of a text there is a maximum number of bytes you need to go forward or backwards to find a character boundary and you can do so with no ambiguity, etc. And a large portion of the writing system suck rant has to do with Chinese (hanzi/kanji/hanja) characters, because there are just so many of them and standardizing them is a fairly difficult process. And it's true; that writing system does suck. It may have some good points, but it's amazing that it's still in use, it would be enormously economically beneficial to move to a simpler, easier to learn writing system. Of course, if you did that and people no longer learned the older, much more cumbersome and complicated system, they would lose access to a large number of older cultural works which do use it, so it's a pretty tough sell. Just to note, Korea actually does use a much simpler, more efficient writing system for the bulk of their text, but they do have a few words that they still use Chinese characters for. One of the reforms in North Korea was to abolish the use of Chinese characters entirely, using only the much simpler hangul writing system. His complaint about Korean is more due to how hangul is encoded in Unicode, which could be considered complex or clever depending on how you look at it; in any other sense, though, hangul is a great, very efficient and easy to deal with writing system.
- backdraw_ 12y agoRegarding point 7, that the collation order is context-dependent: does a title that starts with T come before or after a word that starts with U? What if it starts with "The"?
- asveikau 12y ago> Russian has a very simple alphabet, strictly phonetic. I don't speak Russian but I know enough to say it's not "strictly" phonetic in that there is not always a 1 to 1 mapping of letters to phonemes. For example as an outsider looking at the language I get confused at things like the "г" in "его" being pronounced as a "v" and not "g". In terms of phonetic writing, I personally really like Spanish. Its writing seems the most phonetic amongst languages I have exposure to. (Admittedly limited). With the accent marks you can know the stress of every word even if it's one you haven't seen. You can adjust for regional accents based on spelling ("s" and "z", "ll" and "y" kept distinct even if a lot of speakers say them identically.) There are quirky rules about how a consonant sounds if some vowels come after it but at least it's consistent.
- maga 12y agoI speak Russian and Spanish, and was about to write the same thing. Russian is indeed not strictly phonetic, thought it has a phonemic orthography to a degree. Aside from 'v'/'g' sound, there are bigger problems with vowels reduction when non-stressed 'o' most of the time sounds as 'a', omitting 'ё' and so on. After struggling with English and Russian, Spanish is indeed a delight to read/write. Though obligatory accents make writing a bit cumbersome.
- asveikau 12y agoGlad there are other language nerds on HN. The o/a thing is not totally intuitive to my foreign ears but I'm willing to forgive it as a phonetic feature of the language and less to do with spelling. (I'm reminded of how older people in my [American] family used to say words like "potato", or certain northeastern US pronunciations of words like "Florida" - I guess I have little trouble seeing how o/a can be a flexible concept for some.) Similarly I'm sometimes not sure when "e" becomes "je", but after listening to people speak I think I get something of an intuition...
- maga 12y agoThe problem with o/a is that in some dialects they indeed pronounce 'o' instead of 'a'. Pronouncing 'a', or 'akanye', as it's done in Moscow, became the right way and was imposed through the education system throughout the Soviet Union. Hence, not doing so may be perceived as a sign of a low education level/social status.
- fractalb 12y agoso, if someone has to develop a text(English)-->voice, or voice-->text(English) application, how many special cases would the developer have to handle?
- Sami_Lehtinen 12y agoThis is non technical point but english is broken on other level. As Finnish person I find it ridiculous when people have long discussions about how to pronounce something. Shouldn't it be immediately clear for everyone how something is written or pronounced. Those thing should be 100% directly exchangeable. If I just make up a word and say it Finnish people can write or read the word without any problems. Also all kind of exceptions to generic simple rules should be dropped, just to simplify grammar.
- oranguntan 12y agoThat guy will have a bad surprise about how English 'has simple sorting rules' when someone expects names such as 'Saint Thomas' to sort in the same order as 'St. Thomas' and that somehow 'St.' may also stand for 'street' depending on the order, so that "Thomas St.' should compare equal to 'Thomas Street', and 'Thomas, St.' is probably referring to 'Saint Thomas'...
- UrMomReadsHN 12y ago>But the winner (loser?) here is Serbian, which in some places uses both Latin and Cyrillic characters interchangeably! When I was in Sarajevo once it a while you'd see writing with Latin characters, once in a while with Cyrillic characters and I also saw writing in Arabic. All on the same street. Also Bosnian used to have a third alphabet - Arebica, a variant of the the Perso-Arabic script. Also the license plates in Bosnia and Herzegovina only contain the letters that are in both the Latin and Cyrillic alphabet - A, E, O, J, K, M, T.