| #
d4f83172 |
| 31-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
code style: line breaks
|
| #
90fb952c |
| 31-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
code style: operator spacing
|
| #
177d6836 |
| 31-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
coding style: control flow whitespaces
|
| #
d868eb89 |
| 30-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
codestyle adjustments: function declaration braces/spaces
|
| #
8c7c53b0 |
| 30-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
codestyle adjustments: class declaration braces
|
| #
c1482d1c |
| 30-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
codestyle adjustments: function argument spacing
|
| #
24870174 |
| 29-Aug-2023 |
Andreas Gohr <andi@splitbrain.org> |
Apply rector fixes to the rest of inc
|
| #
8cbc5ee8 |
| 10-Jun-2019 |
Andreas Gohr <andi@splitbrain.org> |
replaced deprecated utf8 functions
For now this uses full qualified namespaces, sensible imports may come later.
|
| #
963c6934 |
| 24-Feb-2019 |
Andreas Gohr <andi@splitbrain.org> |
PSR2 adjustments for SafeFN
the renamed methods were not used in any known plugin
|
| #
08aad3a3 |
| 31-Mar-2017 |
Takamura <plehanov.v@gmail.com> |
I supplemented the existing comments on the methods in which there was not enough information to the standard phpDoc.
|
| #
5a9597bb |
| 31-Mar-2017 |
Takamura <plehanov.v@gmail.com> |
I supplemented the existing comments on the methods in which there was not enough information to the standard phpDoc.
|
| #
f50a239b |
| 31-Mar-2017 |
Takamura <plehanov.v@gmail.com> |
I supplemented the existing comments on the methods in which there was not enough information to the standard phpDoc.
|
| #
e8b5a4f9 |
| 28-Jul-2012 |
Andreas Gohr <andi@splitbrain.org> |
fix E_STRICT errors FS#2427
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
fix E_STRICT errors FS#2427
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.
show more ...
|
| #
63703ba5 |
| 16-Mar-2012 |
Andreas Gohr <andi@splitbrain.org> |
coding style updates
|
| #
344763ad |
| 02-Apr-2011 |
Christopher Smith <chris@jalakai.co.uk> |
FS#2122 alter SafeFN safe and post indicator characters.
Note, any filenames encoded with the previous SafeFN scheme will need to be converted to the new scheme. Users of the old SafeFN scheme shou
FS#2122 alter SafeFN safe and post indicator characters.
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.
show more ...
|
| #
8bddd94e |
| 26-Oct-2010 |
Adrian Lang <dokuwiki@adrianlang.de> |
Fix SafeFN-encoded file names
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 no
Fix SafeFN-encoded file names
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.
show more ...
|
| #
dcee16d6 |
| 04-Apr-2010 |
Christopher Smith <chris@jalakai.co.uk> |
Update SafeFN class, simplify and improve performance
|
| #
70e083ce |
| 04-Apr-2010 |
Christopher Smith <chris@jalakai.co.uk> |
class for safely encoding filenames
This class tries to satisfy the following requirements:
* all ASCII alphanumeric chars in the input should stay the same ASCII alphanumeric chars in the ou
class for safely encoding filenames
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.
show more ...
|