Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #22363, comment 32


Ignore:
Timestamp:
11/16/2013 04:51:10 AM (12 years ago)
Author:
p_enrique
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #22363, comment 32

    v1 v2  
    77  - UTF-8 filenames work OK on WordPress on a *nix platform.
    88  - Percent-encoded filenames work on any platform, but make the filename 6 times longer in certain scripts, such as Cyrillic ('%D0%B6' for the character 'ж', for example).
    9   - The maximum file name length under NTFS is 259 characters including the path.
     9  - The maximum file name length under NTFS is 259 characters including the path. 4
     10  - Percent-encoded filenames are not a solution. <img src='ca%C3%B1o.jpg'/> will 404 even though the file 'ca%C3%B1o.jpg' exists, since the server decodes the request to 'caño.jpg'.
    1011  - remove_accents() is only a partial solution since 1) it has no support at all for non-Latin based scripts and 2) it doesn't do anything with such things as curly quotes, dashes, copyright symbols or other similar things (which are included in sanitize_title_with_dashes())
    1112