00:07:52 Unstable branch on CRAWL.XTAHUA.COM updated to: 0.24-a0-441-g27f0392e16 (34) 00:09:18 Stable (0.23) branch on CRAWL.XTAHUA.COM updated to: 0.23.1-79-g0e89c35649 01:38:24 Unstable branch on crawl.develz.org updated to: 0.24-a0-441-g27f0392 (34) 02:10:17 Windows builds of master branch on crawl.develz.org updated to: 0.24-a0-441-g27f0392 03:00:05 Monster database of master branch on crawl.develz.org updated to: 0.24-a0-441-g27f0392 03:08:54 ziggurnaut (L5 KoAM) Crash caused by signal #15: Terminated (D:3) 03:12:01 Unstable branch on crawl.beRotato.org updated to: 0.24-a0-441-g27f0392 (34) 04:28:54 -!- amalloy is now known as amalloy_ 09:08:51 -!- jfcaron_ is now known as jfcaron 11:22:44 Stable (0.23) branch on underhound.eu updated to: 0.23.1-79-g0e89c35649 13:41:52 -!- Psymania_ is now known as Psymania_phone 14:47:30 I sort of am coming to think that basically all of the upper / lowercase / tolower /toupper calls should be locale insensitive (because crawl breaks horribly if they do anything weird to ascii chars, the error in #846 is just the tip of the iceberg), but it seems like this is likely to break other localizations somehow 14:48:53 do we still have localizations? I though they were already on the way out, because the Polish ones demonstrated they didn't really work or something like that? 14:49:52 well, without constant maintenance I think they tend to gradually lose relevant pieces, and there hasn't been maintenance in a while, but we still have lots of existing partial ones + infrastructure for it 14:50:05 no idea what the state of them is really 14:50:11 what was wrong with the polish ones? 14:50:38 we've had some contributions for iirc russian and maybe others since I've been a dev 14:50:41 Polish is rather more complex than C / C++ locale stuff is prepared to deal with 14:51:01 1kb provided a number of examples of things in crawl that it couldn't do correctly 14:51:45 iirc 14:56:25 yeah, I'm sure it's a mess 14:56:47 but I wouldn't want to break whatever does exist any further 14:59:28 Hi, I have a quick question/proposal. When you read-id ?acquirement, you are stuck in the choice screen; if you care about looking at your dump first (or sharing your characters with others for advice), you need to remember to press # before each read-id until you know ?acquirement 15:00:20 what about adding a command to that screen: when you press # there it updates the dump and shows you the dump, as if you had pressed ?# 15:01:30 I believe I could make a PR for this without too much trouble, but I wanted to see if there'd be any interest in it or other ideas about how to proceed, first 15:03:49 that's probably reasonable to do 15:03:52 I'm also a little hazy on how likely effort spent on identification interactions is to be soon-wasted. Maybe improving the experience of read-id-ing is not worth spending time on? 15:04:47 no one has tried to remove id lately, though it's been getting pared down 15:05:14 OK, thanks 15:13:26 -!- amalloy_ is now known as amalloy 18:20:24 i think a dev was planning to work on changing ?acq to show the item it would generate for each category 18:20:27 ??plan 18:20:27 plan[1/2]: https://github.com/crawl/crawl/wiki/0.24-Development-and-Release-Plan 18:20:59 under "Despoil Acquirement". I don't think any work has begin so you could just implement that instead :^) 20:32:55 -!- amalloy is now known as amalloy_ 21:06:03 /quit 23:34:17 -!- ProzacElf_ is now known as ProzacElf