Rename requests declined

Hello! I declined your requests to replace curly apostrophes. It doesn't fall under the criterion 6 which concerns specific technical problems (double or wrong extensions, obscure unicode symbols which cause problems, etc.), and it doesn't include curly apostrophes. Please review the file renaming policy before making further requests. Deltaspace42 (talk) 14:57, 10 May 2026 (UTC)

@Deltaspace42: I am fully aware of file renaming policy. Last time it was not a problem for another mover when I made exactly the same request. It is either criterion 3, 4 or 6 so I went with 6, because of last time. The ’curly apostrophe’ is not a standard symbol as you need to either type ALT+0146 or use a third-party tool to write it. Therefore, all those files should instead have 'straight apostrophe' in their names as it is the standard in all keyboards (physical or digital) – sbaio 15:16, 10 May 2026 (UTC)

Many files do not use ASCII symbols (e.g. Japanese characters, Polish with diacritics), so replacing non-standard symbols is not a valid reason to rename files. I noticed that some file movers agreed to rename a couple of files previously (since you didn't create a mass rename request for 20+ files last time), but generally, the files shouldn't be renamed just to fix curly apostrophes. Deltaspace42 (talk) 15:41, 10 May 2026 (UTC)

It should be renamed, because it creates problems on English Wikipedia whose Manual of Style says that curly quotations and apostrophes should not be used. Therefore, editors who fix grammar and punctuation errors usually use tools/gadgets (Wikipedia's or browser's extensions). Those tools/gadgets ignore if it is a file name and change it from curly to straights apostrophes, which then breaks it and other editors or bots need to fix the file name (if original editor does not see it after review before publishing the edit). I see that you will not change it despite my observations so there is no need to discuss this further. – sbaio 16:54, 10 May 2026 (UTC)