summaryrefslogtreecommitdiff
path: root/inc/SafeFN.class.php
Commit message (Collapse)AuthorAge
* fix E_STRICT errors FS#2427Andreas Gohr2012-07-28
| | | | | | | | This commit fixes all E_STRICT messages shown when running the test suite. There might be more problems not covered by tests, yet. For compatibility reasons with plugins, E_STRICT errors are still supressed.
* coding style updatesAndreas Gohr2012-03-16
|
* FS#2122 alter SafeFN safe and post indicator characters.Christopher Smith2011-04-02
| | | | | | Note, any filenames encoded with the previous SafeFN scheme will need to be converted to the new scheme. Users of the old SafeFN scheme should not use this new scheme until after converting their filenames.
* Fix SafeFN-encoded file namesAdrian Lang2010-10-26
| | | | SafeFN encoding now always end the encoding block by appending a dot at the end of the file name. This is necessary since the file name may get an extension which is not encoded.
* Update SafeFN class, simplify and improve performanceChristopher Smith2010-04-04
|
* class for safely encoding filenamesChristopher Smith2010-04-04
This class tries to satisfy the following requirements: * all ASCII alphanumeric chars in the input should stay the same ASCII alphanumeric chars in the output * the resulting string should be as short as possible * the operation needs to be reversable without any data loss * the resulting ASCII string should be case insensitive * there should be no restriction on the input length * the whole UTF-8 range should be allowed using it creates a way to store UTF-8 in filenames even if the underlying filesystem does not support UTF-8. It is also pretty robust when files are moved between various filesystems and it creates shorter filenames than the currently used urlencoding.