+AnnaMoritz Posted August 29, 2016 Share Posted August 29, 2016 (edited) Recently I noticed that ` and ´ that were ment to stand as single entities are displayed on the following letter, but only in some webbrowsers like Firefox (48.0.2) and Google Chrome (Version 52.0.2743.116 m). Before it was 'That's right. That´s wrong. And that`s also wrong.' Both ` and ´ were not shown above s before, now ´ and s sometimes give ś like 'Thatś wrong'. (I don't know how to put ` on s outside of geocaching.com) If people use ` and ´ where ' or ’ (Alt-0146) is correct, using `and ´ might be at own risk in normal text. But for cache titles and usernames it really does look ugly if e.q. s`gurkerl is shown as sg̀urkerl. Is this change caused by some new script that should improve handling of Markdown and is that going to stay? (For new logs ´s is shown as ś in editor window and ` causes formatting if you don't escape it by using > resulting in quote, but also old logs are affected.) Edited August 29, 2016 by AnnaMoritz Quote Link to comment
+kunarion Posted August 29, 2016 Share Posted August 29, 2016 (edited) Is this dependent on particular language preference settings? Are your browsers set to languages other than "English (United States)". Mine's set to US English, and I don't see the apostrophe above an "S". I tried various symbols in "That's", and they work as expected. But in another language setting, a certain symbol before a letter may be a shortcut to type a diacritic. I do see the strangeness between how a cache page shows a user name and how it is shown in the Profile page: Instead of symbols in a login name which are guaranteed to be problematic, I just make a really cool avatar. That's looking good. Edited August 29, 2016 by kunarion Quote Link to comment
+AnnaMoritz Posted August 30, 2016 Author Share Posted August 30, 2016 When not logged in and language is set to German retrieving the page is slow enough to see from screenshots in which 0.2 seconds the change happens for cache titles, here are 3 pictures. Maybe someone can identify where the change happens. With language english and/or logged in I didn't see the 'correct' title at all when opening the page, only like in last screenshot. Cache title OK Cache title still OK, Icon for Unknown loaded Cache title already changed, new font in Cache title and two lines in info box added. Quote Link to comment
cezanne Posted August 30, 2016 Share Posted August 30, 2016 Is this dependent on particular language preference settings? Are your browsers set to languages other than "English (United States)". Mine's set to US English, and I don't see the apostrophe above an "S". I tried various symbols in "That's", and they work as expected. But in another language setting, a certain symbol before a letter may be a shortcut to type a diacritic. However that does not make sense for German as acute and grave accents do not appear there and AnnaMoritz mentioned that she uses German in the language setting. Are you using the same version of Firefox than AnnaMoritz? Mine is older and not under Windows. Quote Link to comment
+AnnaMoritz Posted August 30, 2016 Author Share Posted August 30, 2016 'Normal' representation in IE11 11.0.33 [de-AT],[en-US] and text-only browser WebbIE 4.5.1.0 (German) 'combined diacritics' in Firefox 48.0.2 [de-AT],[en-US], Opera 39.0.2256.48 [de-AT],[en-US], Chrome Version 52.0.2743.116 m [de-AT],[en-US], Vivaldi 1.3 (German, English) To me it doesn't seem to be language dependend (but from all variants where combined diacritics occur, FF + not logged in at geocaching.com + language german is somewhat slow in preparing the page and lets me see 'Scarlett´s' before it changes to combined diacritics) Quote Link to comment
cezanne Posted August 30, 2016 Share Posted August 30, 2016 To me it doesn't seem to be language dependend I agree. I now have tested it under Firefox 48.0.2 (Windows) and can confirm that the same happens for me although I always use English in any language settings. Quote Link to comment
+HHL Posted August 30, 2016 Share Posted August 30, 2016 I like this built-in Deppendetektor. Hans Quote Link to comment
+kunarion Posted August 31, 2016 Share Posted August 31, 2016 (edited) Yes! I'm seeing this same effect in Google Chrome (not IE and not Firefox), using "English (United States)". The "acute accent" followed by the letter "s" which somehow combines to form that particular "ś" symbol seen above, looks like this in the HTML source code of the cache pages: I don't know exactly how that "...#180" character code is getting into the page -- is it being ALT-typed that way deliberately? Some browsers are showing it just fine as that goofy backwards apostrophe acute accent thing (Umm... what is the purpose of not using a plain old apostrophe... the one a couple keys to the right of the "L" on a PC keyboard? Then we wouldn't even have this problem. ). Strangely, when I use that code in an HTML page I create myself, it displays as an acute accent, not as an "ś", even in Chrome. I wonder if there's something strange going on in the cache web page style sheets (CSS)? If I paste the exact character code ("...#180") here in this Forum, the code is automatically stripped and changed into the acute accent. In this form it looks fine to me in any browser: s´gurkerl Scarlett´s Myfty Edited August 31, 2016 by kunarion Quote Link to comment
+AnnaMoritz Posted August 31, 2016 Author Share Posted August 31, 2016 If I enter something into various input fields, only the input field of geocaching logs in FF, Chrome etc. enforces combined diacritics in input field and result. Everywhere else, also in FF (and also copying from the garbled input field into a html file shows the 'real content') gives ungarbled characters. It may depend on input keyboard, on German keyboards only aeiouyAEIOUY get ´ on them when pressing ´ and then the letter (in other languages also cgjklrswCGJKLRSW and maybe more letters may have acute on them), to escape 'possible combinations' ´+space+letter is used, for all other characters no combining happens when pressing acute before the letter and the acute is shown before the letter. But this Markdown implementation used on various browsers ignoring more than 1.5 of 2 spaces really seems a bit overboard to me. Perhaps they should note there are (at least) four different characters for 'acute above', for combining e.g. (U+0301 html ''+'769'+';') and (unpredictable) results like x́yz and for spacing e.g. (U+00B4 html ''+'180'+';') to obtain x´yz. Input field for logs on geocaching.com and the result in newest versions of Chrome, FF, Opera, Vivaldi (Windows, German keyboard): Input and Output everywhere else (Windows, German keyboard): áéíóúÁÉÍÓÚýàèìòùÀÈÌÒÙ` acute accent+t ´t acute accent+space+t ´t acute accent+space+space+t ´ t acute accent+space+space+v ´ v acute accent+t+x ´tx z+acute accent+t+x z´tx acute accent+space+t+x ´tx z+acute accent+space+t+x z´tx z+acute accent+space+space+t+x z´ tz z+backtick/grave accent+space+t+x z`tx Spacing grave or backtick is another field as this is (in contrast to ´) used for Markdown synatx. HHL's comment politely paraphrased as 'intelligence test' seems unfair to me concerning usernames and cache titles, they don't need to follow any grammar rules nor othography nor other reasoning. If Groundspeak allowed whatever characters for usernames and cache titles then they should be displayed like they were presented to the user when choosing them, not in some garbled version caused by Groundspeak's implementation of Markdown or whatever. You also never can know whether there is more to it, the characters also may stand for an manifestation of more or less 'artistic' design purposes or sometimes might also be a central part of a puzzle or whatever you might think of. For writing logs I don't see any objective reason why people should use ´ and ` instead of ', so I don't mind that much if such logs get garbled, although sometimes the result is a little bit more tiring to read if 'omitting markers' are ruined visually. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.