Universal plugin which combines the functionality of many other plugins. Wrap wiki text inside containers (divs or spans) and give them a class (choose from a variety of preset classes), a width and/or a language with its associated text direction.

This plugin gives you the ability to wrap wiki text inside containers (divs or spans) and give them

1. a certain class (with loads of useful preset classes)
2. a width
3. a language with its associated text direction

It potentially replaces a lot of other plugins and is IMHO the better alternative for many. There is one exception: It currently lacks ODT support. If you need ODT support, you might want to take a look at similar plugins.

It fully replaces: plugin:class, plugin:divalign, plugin:div_span_shorthand, plugin:side_note, plugin:tip, plugin:clearfloat, plugin:emphasis, plugin:hide, plugin:hilited, plugin:important_paragraf, plugin:important_text, plugin:noprint, plugin:pagebreak, plugin:wpre, plugin:lang, plugin:ltr
It partly replaces: plugin:box, plugin:layout, plugin:note, plugin:styler, plugin:typography, plugin:color, plugin:columns, plugin:fontcolor, plugin:fontfamily, plugin:fontsize, plugin:fontsize2, plugin:highlight, plugin:tab, plugin:tablewidth

The plugin comes with an example page, which should explain a lot and looks like this in the default template:

Basic Syntax:

<WRAP classes width :language>
"big" content
</WRAP>

or
<block classes width :language>
"big" content
</block>

or
<div classes width :language>
"big" content
</div>

An uppercase <WRAP> (or alternatively <block> or <div>) creates a div and should be used for “big” containers, surrounding paragraphs, lists, tables, etc.

<wrap classes width :language>"small" content</wrap>

or
<inline classes width :language>"small" content</inline>

or
<span classes width :language>"small" content</span>

A lowercase <wrap> (or alternatively <inline> or <span>) creates a span and should be used for “small” containers, inside paragraphs, lists, tables, etc.

Please note, some things won't work with spans: alignments (including alignments generated by changing the text direction), multi-columns and widths if the according wrap isn't floated as well.

The following classes are currently available:

class name	description/notes
columns – similar to columns, side_note, styler, tip
column	same as left in LTR languages and same as right in RTL languages
left	same as column, will let you float your container on the left
right	will let the container float right
center	will position the container in the horizontal center of the page
col2..col5	will show the text in multiple columns (2, 3, 4 or 5), only works in modern browsers (Firefox, Chrome and Safari)
alignments – similar to divalign, columns, styler – don't work with spans!
leftalign	aligns text on the left
rightalign	aligns text on the right
centeralign	centers the text
justify	justifies the text
boxes and notes – similar to box, note, tip
box	creates a box around the container (uses colours from style.ini)
info (was information in first version)	creates a blue box with an info icon
important	creates an orange box with an important icon
alert ( was warning in previous versions)	creates a red box with a alert icon
tip	creates a yellow box with a tip icon
help	creates a violet box with a help icon
todo	creates a cyan box with an todo icon
download	creates a green box with a download icon
round	adds rounded corners to any container with a background colour or a border (only works in modern browsers, i.e. no IE)
danger	creates a red danger safety note
warning	creates an orange warning safety note
caution	creates a yellow caution safety note
notice	creates a blue notice safety note
safety	creates a green safety note
marks – similar to hilited, emphasis, important_paragraf, important_text
hi	marks text as highlighted
lo	marks text as less significant
em	marks text as especially emphasised
typography (not recommended) – similar to typography, styler, color, fontcolor, highlight, fontsize, fontsize2, fontfamily removed since version 2011-05-15 (for more information, see below)
sansserif, serif, monospace	changes the font family
bigger, muchbigger, smaller	changes the font size
fgred, fggreen, fgblue, fgcyan, fgviolet, fgyellow, fggrey, fgwhite, fgblack	changes the font colour
bgred, bggreen, bgblue, bgcyan, bgviolet, bgyellow, bggrey, bgwhite, bgblack	changes the background colour
miscellaneous
clear	similar to clearfloat, should preferably be used with divs, i.e. uppercase <WRAP>s
hide	hides the text per CSS (the text will still appear in the source code, in non-modern browsers and is searchable)
noprint	displays text on the screen, but not in print, similar to noprint
onlyprint	displays text only in print, but not on the screen
pagebreak	forces a new page in printouts (not visible on the screen), similar to pagebreak
nopagebreak	tries to avoid a pagebreak in printouts (not visible on the screen)
spoiler	shows white text on a white background, only to be revealed by highlighting it; similar to hide
indent	indents the text, could be used instead of tab
outdent	“outdents” the text, could partly be used instead of outdent
prewrap	wraps text inside pre-formatted code blocks, similar to wpre

All tables inside a column or box will always be 100% wide. This makes positioning and sizing tables possible and partly replaces tablewidth.

• WRAPs won't export in ODT format
• The PNG icons for the various notes have an alpha transparency which will look ugly in IE6.
• Round corners only work in modern browsers (no IE).
• Multiple columns only work in Firefox, Chrome and Safari.
• After an opening <WRAP> there is one empty line needed before the content, or else there won't be any paragraph, which might lead to unexpected results. (Wraps without a visible content don't need any additional empty lines, e.g. clear or hide.) This was fixed in the latest version (2010-11-20) if used with Anteater.
• Normal DokuWiki Headlines won't work inside any plugin syntax. As a work-around you can use the following two emulated headlines inside any of the columns or boxes/notes:
  • //**__Big Underlined Headline__**// (They will look a bit different in safety notes.)
  • //**Small Headline**//

You probably need to adjust a few of the classes to your template's needs, especially hi, lo and em if you have a dark or otherwise heavily coloured theme.

The classes are easily adjustable and extensible. Any wishes are welcome.

You can set any valid widths on any uppercase <WRAP> container: %, px, em, ex, pt, pc, cm, mm, in. Just set the width before or after or with the classes, e.g.

<WRAP someclass 50% anotherclass>...

You can change the language and the direction of a container by simply adding a colon followed by the language code, like this:

<wrap :en>This text is explicitly marked as English.</wrap>

The text direction (rtl, right to left or ltr, left to right) will get inserted automatically and is solely dependent on the language. The list of currently supported languages is taken from: http://meta.wikimedia.org/wiki/Template:List_of_language_names_ordered_by_code

If you like to mark a text with a different text direction than the default one, you should use divs, i.e. uppercase <WRAP>s. Otherwise the text alignment won't change as well.

This makes it a better replacement of ltr (and lang).

If you like to add your own classes and styles to the plugin, you can simply add the styles for your class preceded by “wrap_” to your user styles.

E.g. if you need a <WRAP myclass>, you edit (or create if it doesn't exist) your conf/userstyle.css and add your .wrap_myclass{} with its style definitions to it. (If necessary, edit conf/userprint.css¹⁾ for the print view, conf/userrtl.css²⁾ for RTL languages and conf/userall.css³⁾ for all styles as well.)

Since version 2010-03-14 you have the possibility to exclude certain class names from being prefixed with “wrap_”. Just add a comma separated list of class names into the config option “noPrefix” in the configuration manager.

in style.css

.dokuwiki div.wrap_note{ /* added */
    background-color: #eee;
    color: #000;
    padding: .5em .5em .5em .5em;
    margin-bottom: 1em;
    overflow: hidden;
}

call in DW-page:

<WRAP note>...</WRAP>

The old typography classes were removed in version 2011-05-15. If you need something similar, use the block plugin instead. If you like to have the old typography classes back, they are not lost: They were not completely removed yet, but only put in a comment. To keep using them either remove the comments (search for “typography” in all.css and style.css). Or better (because future-proof) copy them to your own user styles (see above).

From version 2011-05-15 on the plugin includes a helper plugin which you can use to add classes, width and lang/dir to any other plugin.

// get lang from wrap helper plugin
$lang = '';
if(!plugin_isdisabled('wrap')) {
    $wrap =& plugin_load('helper', 'wrap');
    $attr = $wrap->getAttributes($data);
    if($attr['dir']) $lang = ' lang="'.$attr['lang'].'" xml:lang="'.$attr['lang'].'" dir="'.$attr['dir'].'"';
}
 
// add lang to your plugin's output
$renderer->doc .= '<span '.$lang.' class="foo">';

getAttributes() expects the string with “classes width :language”. It returns an array with

• $attr['class']: CSS class(es)
• $attr['width']: width
• $attr['lang'] and $attr['dir']: language and text direction

// get attributes from wrap helper plugin
$attr = '';
if(!plugin_isdisabled('wrap')) {
    $wrap =& plugin_load('helper', 'wrap');
    $attr = $wrap->buildAttributes($data, 'additionalClass');
}
 
// add those attributes to your plugin's output
$renderer->doc .= '<div '.$attr.'">';

buildAttributes() expects the same string as above (“classes width :language”) and an optional string for additional classes, in case your plugin has CSS classes of its own which it needs to reuse. It returns a string with all the attributes prepared for HTML.

• An error occurred while fetching this feed: http://github.com/feeds/selfthinker/commits/dokuwiki_plugin_wrap/master

• ODT support
• and more …

You can help me with translations. There are two files to translate:

• lang/en/lang.php is for the explaining titles on the picker images.
• lang/en/settings.php is for the (currently only option in the) configuration admin.

You can either send me language files to update by email or post them here or in the bugtracker. Please have a look at the available translations first.

• The code reuses parts of the box plugin. Thanks to Christopher Smith.
• The images for the notes are taken from the Human-O2 icon set.
• The toolbar uses images from the Silk Icon Set and the Silk Companion Icon Set.
• Thanks to all contributors: Andreas Gohr, campino2k, Sergio Motta and Danny Lin.

Before reporting any issues (bugs or requests), please first take a look at the FAQ on plugin problems.

You can report any issues either on the Issue Tracker or here in this section.

I've just made the CSS work properly with some custom themes using the git master branch, eg one of my own and typo. the trick is to remove all the .dokuwiki in the different classes with a

perl -pi -e 's/\.dokuwiki//g' *.css

— Nicolas Thauvin 2009/09/09 23:22

Templates should use the .dokuwiki class and many already do (as does the typo template). See more on the dokuwiki class. — Anika Henke 2009/09/18 00:37

Wouldn't it be nice to add quotation box, too …
- chris

Yes, I thought about that, too. But as the blockquote plugin would be semantically much more correct, I recommend using that instead. — Anika Henke 2009/09/18 00:37

Incredibly useful multipurpose plugin I must say. Thanks for that“ Looking forward to intended ODT compatibility.
— Martin 2009/09/14 23:22

<WRAP centeralign>

<WRAP info 60%>

This is some text, text , text , text , text , text , text , text , text , text , text , text , text , text , text , text ,
text , text , text , text , text , text , text , text , text , text , text , text , text , text , text , text , text , text
</WRAP>

[[namespace:something|{{:picture.png|GO}}]]
</WRAP>

The result is the text of the info note is centered. If I use leftalign it aligns the whole box left. How do I get the box text to be left aligned and screen centered? peterennis [at] yahoo [dot] com

To position something you shouldn't use an alignment class, but one of the column classes. In this case it's “center” instead of “centeralign”. (And whenever you use “center” you should also give a width.) If you only want the info box to be centred, you can use <WRAP center info 60%>, and the image could be centred by using the normal DokuWiki syntax. — Anika Henke 2009/10/07 07:47

Like using tab-plugin in some places (perhaps tables)

I sometimes need space above or below a paragraph. Fed up fiddling with HTML, PHP methods so I just use . (dot)
Of course, it shows a dot! Is there an easy solution? peterennis [at] yahoo [dot] com

The best way would be to add your own classes. In this case you could use something like ”topspace“ and ”bottomspace“ and add

.dokuwiki .wrap_topspace { margin-top: 1.5em; }
.dokuwiki .wrap_bottomspace { margin-bottom: 1.5em; }

etc. But this depends highly on your template and in which combination you will use those classes. Just fiddle around with the values to change their effect. (And from the semantic point of view you should probably ask yourself why and if you need that space and find a better name if you find a common usage pattern.) — Anika Henke 2009/10/07 08:05

I think too it depent on your template and the combination of classes. Testing with following code I could find something working for me.

css try differend combinations of height, margin, padding and line-height. The colors are only to see the effect. (%, px, em, ex, pt, pc, cm, mm, in):

div.wrap_testing { width: 100%;                                        border: 2px solid yellow; }
div.wrap_empty1  { width: 100%; height: 2em;                           border: 2px solid red; }
div.wrap_empty2  { width: 100%; margin-top: 2em; margin-bottom: 2em;   border: 2px solid violet; }
div.wrap_empty3  { width: 100%; padding-top: 2em; padding-bottom: 2em; border: 2px solid blue; }
div.wrap_empty4  { width: 100%; line-height: 2em;                      border: 2px solid green;  }

dokuwiki:

\\
<div testing>  <div empty1></div>  </div>
\\
<div testing>  <div empty2></div>  </div>
\\
<div testing>  <div empty3></div>  </div>
\\
<div testing>  <div empty4></div>  </div>

Love this plugin, but the CSS on my page seems to fail CSS3 validity check as a result.

1  	 .dokuwiki div.wrap_round  	 Property -moz-border-radius doesn't exist :  20px
1 	.dokuwiki div.wrap_round 	Property -webkit-border-radius doesn't exist : 20px
1 	.dokuwiki div.wrap_round 	Property -khtml-border-radius doesn't exist : 20px
1 	.dokuwiki span.wrap_round 	Property -moz-border-radius doesn't exist : 2px
1 	.dokuwiki span.wrap_round 	Property -webkit-border-radius doesn't exist : 2px
1 	.dokuwiki span.wrap_round 	Property -khtml-border-radius doesn't exist : 2px 

I'm no CSS expert. Anybody have any suggestions? — michaelrepucci 2009/11/06 22:08

Actually, did some web searches and discovered that since these properties are proprietary, they're not considered part of “valid” CSS, even though they do follow standards. Oh well. When CSS3 is adopted, “border-radius” will replace the proprietary properties and validate. Until then, guess I'll live with it. I'll leave this note here for others who are curious like me. Anyway, nice to have rounded corners :) — michaelrepucci 2009/11/06 22:32

is there any way to skip the generation of the wrap_ “namespace” I'd like to use this for providing a (hidden) geotag on the page like this:

<WRAP hide geo geo-post>  
    <wrap latitude>52.085819</wrap><wrap longitude>5.115348</wrap>
</WRAP>

right now that results in:

<div class="wrap_hide wrap_geo wrap_geo-post">  
    <span class="wrap_latitude">52.085819</span><span class="wrap_longitude">5.115348</span>
</div>

where I would want:

<div class="wrap_hide geo geo-post"> 
    <span class="latitude">52.085819</span><span class="longitude">5.115348</span>
</div>

I wouldn't want to skip the “wrap_” altogether. But it might be a good idea to add a config option for listing all class names which should not be adjusted but taken directly as specified. Then everybody is free to also add other microformat classes and more. I'll implement that as soon as I find the time. — Anika Henke 2010/01/07 01:52

I just implemented this (in the repo). A new release which includes it will follow soon. — Anika Henke 2010/01/31 15:36

                case DOKU_LEXER_ENTER:
                    $wrap = new syntax_plugin_wrap_base();
                    $attr = $wrap->buildAttributes($data);

                    $renderer->doc .= '<div'.$attr.'><p>';
                    break;

The div version of the plugin merges the first two paragraphs into one. The workaround is to leave a line break immediately after the opening

<bare> <html><div class="baretable"></html>
</bare> <html></div></html >

div.dokuwiki div.baretable th,
div.dokuwiki div.baretable td { border: 0px; }

/* tables in columns and boxes should span the whole width */
.dokuwiki .plugin_wrap table {
    width: 100%;
}

<WRAP column>
//**Headline**//
^Column 1 Row 1 |Column 2 Row 1  | 
^Column 1 Row 2 |Column 2 Row 2  | 
^Column 1 Row 3 |Column 2 Row 3  | 
^Column 1 Row 4 |Column 2 Row 4  | 
^Column 1 Row 5 |Column 2 Row 5  | 
</WRAP>

/* tables in columns and boxes should span the whole width */
.dokuwiki .plugin_wrap .wrap_fixsize table {
    width: 100%;
}

            //get width
            if (preg_match('/^\d*\.?\d+(%|px|em|ex|pt|pc|cm|mm|in)$/', $token)) {
                $attr['width'] = $token;
                $attr['class'] = (isset($attr['class']) ? $attr['class'].' ' : '')."wrap_fixsize";
                continue;
            }

            //get id
            if (preg_match('/#([A-Za-z0-9_-]+)/', $token)) {
                $attr['id'] = trim($token,'#');
                continue;
            }

            if($attr['id']) $out .= ' id="'.hsc($attr['id']).'"';

<WRAP tabs>
  * [[Features]]
  * [[Manual]]
  * [[Plugins]]
  * [[Template]]
</WRAP>