::: You're right. That is just what I have in mind when editing old revisions.
::: In regard to my wiki, along some days, I can put on my homepage here, some snapshots with this subject treated here, and other "exotics" features. :)
::: (Still it isn't mature so far, because I have pending exactly 100 major bugs or patchs, others 100 minor bugs or patchs, and 50 minor tweaks. It's still a wiki tangled and matted). But the snapshots is a good beginning. ;)\\
::: Best regards, --JuanmaMP
Other subject: where I can begin fix from to avoid in copy-paste urls like: \\
http://gypark.pe.kr/wiki/UseModWiki소스수정/이전수정본화면에서더블클릭, not become like: http://gypark.pe.kr/wiki/UseModWiki%EC%86%8C%EC%8A%A4%EC%88%98%EC%A0%95/%EC%9D%B4%EC%A0%84%EC%88%98%EC%A0%95%EB%B3%B8%ED%99%94%EB%A9%B4%EC%97%90%EC%84%9C%EB%8D%94%EB%B8%94%ED%81%B4%EB%A6%AD
\\
For the time being, I have to paste in two steps, first, the latin characters, then paste korean characters beside it. \\
Thanks
: Hmm... what do you want exactly, the former form(with multibyte character) or the latter form(with %-encoded)? If you like the latter, use "Permalink" link in the bottom of every page. If you prefer the former... as far as I know, it depends on the behavior of web browser. Firefox always convert URL to %-encoded form. IE doesn't. I don't know how to control it.
: Really? Then, users that use, for instance, korean, chinese, japanese, only for that cause, have one more reason for browsing with Explorer. D'oh! --JuanmaMP
Hi, Raymundo, \\
I was having a look at URLs converted to percent enconding, and if I decoding (thanks to a snippet code from you: &DecodeUrl). I turn again to decoding at: \\
sub DoPostMain {
...
$string =~ s/$FS//g;
+ $string = &DecodeUrl($string);
$summary =~ s/$FS//g;
... \\
then WYSIWYG ! on textareas and saving texts, and urls goes well.
Otherwise, Don't touching the encoding saved texts, but, \\
sub BrowsePage {
...
- $fullHtml .= &WikiToHTML($Text{'text'});
+ $Text{'text'} = &DecodeUrl($Text{'text'});
+ $fullHtml .= &WikiToHTML($Text{'text'});
...
}
The first option (before) doesn't preserves the encoding but it's more eye-friendly. Heterodoxal, I guess. \\
Good morning.
: I'm sorry but I can't understand what the purpose of this patch is. Could you please explain or show me example about the difference between before and after this patch?
Of course. There's 3 snapshot. \\
In 1, I copy and paste url like this page. \\
In 2, after Preview, and with the patch. \\
In 3, after Preview, without the patch. \\
if there's url that mixes latin and korean characteres. Then it encodes to %-encoded form, as you know. With this patch, the characters are as I see them in the url (without %-encoded). Have I explained it better?. \\
The purpose is more eye-friendly if there's no side effects, and it can be applied functionally in other purpose, for example I need decoder for edit with double clic when the page is all korean characters, because encodes to %-encoded. But I see that this last don't happen to you. My core script is still based on Usemod, and I use to browse, Chromium. But the first effect (snapshot 3) still hapen from here with your website.
Now, the snapshots ...
Here: https://picasaweb.google.com/109809234853259868273/19DeJulioDe2012
: Ooops, I was thinking "Encode url" until now... Yeap, I see what you are saying now. :-D \\
\\
I'm not sure what side effects this patch may bring, so I need time to consider it. But it is a good idea, I think. Thank you!
ok :)
----
[[위키위키분류]]