[cl-wiki-devel] Encoding question and a patch
Hi, One question, One patch :) Question: We want to maintain a turkish wiki. If we edit a page containing UTF characters (dedicated for turkish symbols) they are all translated to unknown stupid characters. By each addition, it goes worse... 1) ş 2) ÅŸ 3) ÅŸ 4) ÅŸ etc. I think, #'with-html-output-to-string or #'esc are responsible for that. Any idea? Patch: http://www.vsthost.com/materials/wordpress/patches20050904.tar.gz Changelog: * added url-decode for space character (correct display of page title) * added backup functionality (a trivial way, no versioning or differencing, just puttin' the previous version of the file into a backup folder. useful for emergency...) * exported *wiki-page-list* along with *wiki-url*, *wiki-directory* etc... Note: First, apply Ian's patch and then, mine to cl-wiki-0.0.3. Ian's patch is in the folder as well. Best Regards, --vst
On 2005-09-04 19:23:47, Vehbi Sinan Tunalioglu wrote:
Changelog: * added url-decode for space character (correct display of page title)
Good thinking. I've changed it a bit: Call to TBNL::URL-DECODE at CURRENT-PAGE. The page name should always be decoded.
* added backup functionality (a trivial way, no versioning or differencing, just puttin' the previous version of the file into a backup folder. useful for emergency...)
I must think about it. Don't know if I will put this into the 0.0.4 release. One of the next (after 0.0.4) few important steps is to plan a format and way who to save the pages with metadata, etc. Regards, Stefan
Stefan Scholl wrote:
On 2005-09-04 19:23:47, Vehbi Sinan Tunalioglu wrote:
* added backup functionality (a trivial way, no versioning or differencing, just puttin' the previous version of the file into a backup folder. useful for emergency...)
I must think about it. Don't know if I will put this into the 0.0.4 release. One of the next (after 0.0.4) few important steps is to plan a format and way who to save the pages with metadata, etc.
I would better not use my idea :) This is a very trivial way. You are mentioning a metadata format: This would be nice. Besides, we could employ the "difference" method for handling the versions. --vst
participants (2)
-
Stefan Scholl -
Vehbi Sinan Tunalioglu