Ozaru

Hi. I noticed that you were involved in the Birchington-on-Sea article. I'm currently trying to get the article to Featured Article status and I just wondered if you have any photos of the town which you could be added to the article. Thanks. Epbr123 19:44, 16 May 2007 (UTC)Reply

I don't know how it's gone unnoticed for so long, but your edit here [1] constitutes vandalism. I would trot out the usual template warning, but I'm slightly confused, as you seem to otherwise be quite constructive in your editing. Please refrain in the future. Giles Bennett ^{(Talk, Contribs)} 23:56, 31 December 2007 (UTC) Reply

Scratch all that. I don't think its vandalism, but I'm not sure its appropriate for the article in question, so its removal should stand, in my view. I guess my New Year's resolution could be to look before I leap... ;-) Giles Bennett ^{(Talk, Contribs)} 23:59, 31 December 2007 (UTC)Reply

Hi. When you updated the hibakusha figures in Atomic bombings of Hiroshima and Nagasaki, you added

(There is an unexplained discrepancy of 25 people in the Nagasaki figures, as 185982-182601 = 3381 not 3406.)

I've been tracking these numbers for a while; this sort of change from year to year is pretty common, for whatever reason. Relatives not notifying the record keepers that Grandpa died? See Talk:Hibakusha/Numbers of Hibakusha section.
—WWoods (talk) 17:52, 11 August 2020 (UTC)Reply

Thanks - although if it were e.g. "Relatives not notifying the record keepers that Grandpa died in 2019" I'd expect the figures to say (e.g.) count up to 2018 = 180,000, up to 2019 = 181,000, up to 2020 = 182,001 with Grandpa being a 2019 death added to the register in 2020 [the wording is as such, 'confirmed victims added to the register this year', not 'died this year']. So if it were extra victims identified, I think the 'total as of last year' plus 'number identified this year' should still make 'total as of this year'. My guess is that there's a decrease because either (a) Someone has identified duplication, e.g. Yamada Takashi 1944-2019 is actually the same person as Yamada Takashi 1943-2018 so one of them needs to be removed from the total count; or (b) Someone has requested removal from the list, e.g. please remove my father Yamada Takashi from the list because the prejudice against Hibakusha is making it difficult for me to marry/find work/etc. But that's just speculation from my side - I've not seen any official explanation, which is partly why I included the comment in the article (to see if someone else could find an explanation; but also to prevent others from commenting "these figures don't add up! must be fake!"). I hadn't noticed that the complete figures for numerous years are on the Talk page, so thanks for alerting me to that (and big thanks for putting them there). Maybe they could be added to the main article as a graph? (See example here.) It does support the common cry of the people of the Hiroshima that 'this is not just a story in the history books'. Incidentally, I find it astonishing that the 'total' number has been decreasing steadily since 2013! There must be some explanation - be it duplication, requests, or something else. Maybe I'll copy your figures across to the JP page and see if others there comment. Ozaru (talk) 13:09, 12 August 2020 (UTC)Reply

Out of curiosity, does the technique xxxx Alt+X (as described at Unicode input#In Microsoft Windows) work for you with Japanese keyboard mapping on? Does A3 Alt+x deliver a £ sign? . --John Maynard Friedman (talk) 18:45, 14 September 2020 (UTC)Reply

Sadly no - I had tried that too. It does work in Word, Wordpad, etc. (as does Alt+0163) but not in plain-text scenarios. Maybe there's something deep inside Windows saying 'this application is truly Unicode-compliant' (for Word etc.) versus 'this application is old-fashioned codepage-based' (for Notepad etc.). It's amazing (and irritating) to think that even in this 64-bit age, the Visual Basic Editor doesn't support Unicode and Excel can't save Unicode CSV files. So much for I18N. Ozaru (talk) 20:29, 14 September 2020 (UTC)Reply