| 00:30.06 | *** join/#wowuidev harl (~harl@unaffiliated/harl) |
| 01:25.55 | *** join/#wowuidev pompy (~Mike@2601:87:4101:92f0::427) |
| 01:41.49 | *** join/#wowuidev yalb (xsbot@lua/bot/yalb) |
| 02:45.13 | *** join/#wowuidev Andols (~yaaic@217-209-12-6-no170.tbcn.telia.com) |
| 03:24.47 | *** join/#wowuidev purl (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 03:24.48 | *** topic/#wowuidev is BC Dinner Sign Up: https://bit.ly/2mV8xKi || WoW Classic Addon Cat: https://www.wowinterface.com/downloads/cat160.html || 8.2.5 ToC: 80205 || 1.13 ToC: 11302 || http://pastebin.com || Discord: https://discord.gg/sVQCHr5 || Battletags: http://bit.ly/2MAEFxk || This channel is logged, via purl |
| 03:59.39 | jadiilelz | i noticed that wow supports 'some' ascii but not all. is there a chart or list that you can think of which i could refer to know 'which' precise values are supported? ty! |
| 05:14.25 | *** join/#wowuidev purl (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 05:14.25 | *** topic/#wowuidev is BC Dinner Sign Up: https://bit.ly/2mV8xKi || WoW Classic Addon Cat: https://www.wowinterface.com/downloads/cat160.html || 8.2.5 ToC: 80205 || 1.13 ToC: 11302 || http://pastebin.com || Discord: https://discord.gg/sVQCHr5 || Battletags: http://bit.ly/2MAEFxk || This channel is logged, via purl |
| 05:43.09 | *** join/#wowuidev Andols2 (~yaaic@2a00:801:42f:7d62:a960:b4f:5226:c9a7) |
| 05:59.37 | *** join/#wowuidev greedom (~greedom@mue-88-130-54-033.dsl.tropolys.de) |
| 06:00.53 | Chipzz | jadiilelz: false. ASCII is only defined between codepoint 32 and 127, all chars above are subject to codepages. whatever problem you think you're seeing is not specific to WoW |
| 06:01.22 | Chipzz | I would like to suggest you actually google how ASCII works |
| 06:02.36 | Chipzz | WoW does however support unicode, so I'm not even sure what's up with ASCII in the first place |
| 07:42.00 | *** join/#wowuidev Cairenn1 (~Karen@CPE946a77113f89-CM946a77113f87.cpe.net.cable.rogers.com) |
| 08:15.40 | *** join/#wowuidev pompy (~Mike@2601:87:4101:92f0:a131:cb6a:ab87:be44) |
| 10:41.56 | *** join/#wowuidev stolenlegacy (~stolenleg@unaffiliated/stolenlegacy) |
| 11:01.30 | *** join/#wowuidev Elmoe (~Elmoe@24.18.143.238) |
| 11:32.38 | *** join/#wowuidev A-KO (A-KO@136.52.64.157) |
| 11:43.43 | *** join/#wowuidev Yuyuli (~Yuyuli@85-127-63-68.dsl.dynamic.surfer.at) |
| 11:51.05 | *** join/#wowuidev Gethe_ (~Gethe@2605:a601:aa00:e700:4c48:f833:922a:c4d2) |
| 12:59.57 | *** join/#wowuidev Breen (~Breen@80.175.117.105) |
| 14:14.08 | *** join/#wowuidev Industrial (~tom@h146022.upc-h.chello.nl) |
| 14:34.02 | *** join/#wowuidev harl (~harl@unaffiliated/harl) |
| 18:49.08 | Gnarfoz | I see Mr. explain things in the most condescending way possible is still around :D |
| 19:34.44 | Ennea | Gnarfoz, would you rather be left in the dark? |
| 19:36.03 | TheDanW | fonts don't have glyphs for all characters, you'd have to inspect the font you're using to see what is supported |
| 19:37.55 | Gnarfoz | Ennea: that's not what I said ð¤·â |
| 19:53.50 | *** join/#wowuidev eir (eir@freenode/utility-bot/eir) |
| 20:01.58 | *** join/#wowuidev Sintacks (~Syntax@unaffiliated/sintacks) |
| 20:04.56 | Ennea | i guess ;p |
| 20:07.01 | jadiilelz | i think the person reading my request is probably esl |
| 20:14.47 | Gnarfoz | anecdotal evidence suggests he's just an asshole :P |
| 20:15.56 | Gnarfoz | he's not wrong, though - your question suggested at least a confusion as to what ASCII means |
| 20:45.31 | Chipzz | Gnarfoz: I don't think I said that in a condescending tone |
| 20:46.28 | Chipzz | and quite frankly I think the answer I gave was actually useful |
| 20:46.39 | Chipzz | also, nothing wrong with telling people to google sth |
| 20:48.02 | Chipzz | Gnarfoz: also, "just an ashhole", well, at least I'm not the one slinging random insults around |
| 20:48.27 | Gnarfoz | far from random |
| 20:49.00 | Chipzz | oh so you believe you have a reason to throw insults at me? |
| 20:49.15 | Chipzz | even if that were the case, actually doing so shows a lack of maturity |
| 20:52.17 | Gnarfoz | oh woe me. maybe consider how mature answering a question with "false" is. |
| 20:52.38 | Gnarfoz | (or rather, that type of question in particular) |
| 20:53.01 | Chipzz | he made an assumption and the "false" was in reference to his assumption |
| 20:56.01 | kd3 | the classic toc changed. I like this new 'breaking changes = new toc#' thing. |
| 20:57.38 | Chipzz | there's absolutely nothing immature about correcting someone when he makes an incorrect assumption IMO. it's a simple discussion about facts. I answered in an IMO neutral way. I didn't call him dumb or use any other kind of insult. That's what you're reading into it |
| 20:57.56 | Alram | i read it the same way tbh |
| 20:58.09 | Alram | "I would like to suggest you actually google how x works" feels kinda douchey |
| 20:58.15 | Alram | but its the internet, so intent is hard to bring across |
| 20:59.01 | Chipzz | it's not douchey, it's a simple "I already gave you half the explanation, further reading for in-depth details is up to you" |
| 20:59.38 | Alram | just saying that i read it the same implied negative way |
| 21:01.09 | Chipzz | wonders what esl is supposed to mean |
| 21:02.19 | Alram | i think it means he suspects english isn't your first language |
| 21:02.45 | Alram | sometimes those people word things a bit too harshly but with good intent, not knowing it might come off as such |
| 21:03.22 | Chipzz | I'm not a native English speaker, but I do consider myself to be fluent |
| 21:03.43 | Alram | it is especially prevalent the more eastern you go i think, which is interesting |
| 21:03.49 | Alram | some languages are more... direct |
| 21:04.06 | Chipzz | anyway if you think someone telling you to google sth is rude, then you probably have too long toes for "the internet" |
| 21:04.47 | Chipzz | I'm in plenty of IRC channels and plenty of forums and telling people to google sth happens all the time |
| 21:05.37 | Alram | yes but words that strengthen a statement like 'actually' or direct answers like 'false' could come off harsh |
| 21:05.45 | Alram | or indeed condescending |
| 21:05.56 | Chipzz | and I believe it was approrpriate since a) I already explained him the relevant parts of his misconception and b) and in-depth explanation of ASCII and codepages is not exactly on-topic here |
| 21:06.39 | Alram | you're taking this way too far :P |
| 21:07.08 | Chipzz | maybe, I just don't appreciate being called an asshole :) |
| 21:07.10 | Alram | it was just a bit of feedback to maybe word things in a way that cant as easily imply a harsh/condescending tone |
| 21:07.27 | Alram | i didn't mean much else with it |
| 21:07.35 | Chipzz | Alram: it's not you I have an issue with :) |
| 21:08.52 | Ennea | kd3, thanks for that heads-up |
| 21:10.25 | Ennea | i feel like what Chipzz said was pretty neutral. just very to the point i guess |
| 21:11.00 | Chipzz | Ennea: thx :) |
| 21:11.53 | *** join/#wowuidev cirdan (~cirdan@69.248.38.199) |
| 21:18.37 | Chipzz | if you want to read an undertone in what I said, it's probably sth along the lines of "The ASCII problem has been around for decades. This is a question you could have avoided, because it's well-documented in several places, which you would have found if you had bothered to research the problem yourself." So I'm using the word 'actually' to suggest doing your own research before asking questions |
| 21:21.12 | Chipzz | and I have been told here in the past to do my own research before asking questions. so... |
| 21:42.59 | *** join/#wowuidev Andols (~yaaic@217-209-12-6-no170.tbcn.telia.com) |
| 22:26.28 | nebula | fixating on using "ascii" wrong when that had nothing to do with the question makes you come off as an pedantic asshole, so... |
| 22:28.30 | Chipzz | you have a very weird definition of both "nothing" and "fixating" |
| 22:29.03 | Chipzz | a) he was asking specifically about ASCII not supporting some characters. his question was about exactly that |
| 22:29.19 | Chipzz | b) fixating? 07:02 < Chipzz> WoW does however support unicode, so I'm not even sure what's up with ASCII in the first place |
| 22:29.34 | Chipzz | I pointed him to unicode which was the correct answer for what he was doing |
| 22:29.53 | nebula | he was asking about glyph support, just because he said ascii didn't require a lecture about what ascii actually is |
| 22:34.39 | *** join/#wowuidev AcidWeb1 (~AcidWeb@londe.iosphe.re) |
| 22:34.48 | *** join/#wowuidev AcidWeb2 (~AcidWeb@londe.iosphe.re) |
| 22:39.48 | Chipzz | then you're reading more into his question than I did. his question didn't mention glyoh support. but for example if your native language is French, chances are that your system is configured to run with a Frnch CP, in which for example é is a codepoint below 255. It's very much possible that he editted a file with such a char in it, and it didn't display correctly (and the correct solution for that woul |
| 22:39.54 | Chipzz | d have been to use unicode é instead) |
| 22:44.14 | *** join/#wowuidev AcidWeb (~AcidWeb@londe.iosphe.re) |
| 23:13.09 | MooreaTv | that idiotic classic addon channel changes is really ruining my day having to come up with crap additional code to work around it... (not even sure which, thought I'd use regular chat but forgot that requires hw event now) |
| 23:14.18 | *** join/#wowuidev Andols2 (~yaaic@217-209-12-6-no170.tbcn.telia.com) |