Loading...
Skip to main content
Navigation and related functionality and content
Features
Requirements
Download
Install
Backup
Upgrade
Help
FAQs
Need Assistance ? Join-us live this Thursday, click for info !
Related content
Find
History: Mise en forme avançée du texte
View published page
Source of version: 11
(current)
{REMARKSBOX(type="warning" title="Attention !")}((Traduction incomplète)){REMARKSBOX} ! Exemples de syntaxe wiki avancée La syntaxe wiki est généralement simple et utile. Cependant, il peut arriver qu'elle porte à confusion ou qu'il serait préférable d'utiliser le (X)HTML. La présente page vise à regrouper vos trucs et astuces permettant de tirer le maximum de la syntaxe wiki. !!Comment insérer un espace insécable En (X)HTML, les codes __~amp~nbsp;__ ou __~amp~#160;__ permettent d'insérer l'espace insécable, mais que faire dans une page wiki? Eh bien il suffit d'utiliser __~np~~hs~~/np~__ qui est un raccourci de "hard-space"~hs~: {CODE(caption="Code",wrap="1")}Pour certaines langues comme le français, l'espace insécable est très utile. Il permet d'éviter que certains symboles comme le pourcentage, le degré ou le deux-points ne se retrouvent sur une ligne différente du mot qu'ils suivent quand l'utilisateur modifie l'affichage. Ainsi, la syntaxe pour une date correctement formatée qui restera toute sur la même ligne, on écrirait 13~hs~décembre~hs~2007. {CODE} La dernière phrase (avec l'espace insécable)~hs~: Ainsi, la syntaxe pour une date correctement formatée qui restera toute sur la même ligne, on écrirait 13~hs~décembre~hs~2007. La même sans l'espace insécable~hs~: Ainsi, la syntaxe pour une date correctement formatée qui restera toute sur la même ligne, on écrirait 13 décembre 2007. C'est ce qu'on cherche à éviter. Beaucoup de langues, dont le français, utilisent l'espace comme séparateur des milliers dans les nombres et comme séparateur entre le chiffre et le symbole de la devise. En français, certains symboles sont toujours précédés par l'espace insécable~hs~: ~hs~: ~hs~° ~hs~% À l'intérieur de guillemets, on doit trouver l'espace insécable après le guillemet ouvrant et avant le guillemet fermant. Veuillez noter qu'en français, on utilise les caractères suivants~hs~: « » Le symbole ~np~"~/np~ appartient à une autre culture (l'anglais). ^Translation in progress.^ !!How to get multiple lines in a table cell {CODE(caption="Code",wrap="1")} ||r1c1|r1c2%%% Here is my first line %%% Here is my second line %%% Here is my third line r2c1|r2c2|| {CODE} generates: ||r1c1|r1c2%%% Here is my first line %%% Here is my second line %%% Here is my third line r2c1|r2c2|| !!How to make a bullet list in a table cell? (no solution yet) Doesn't look possible with current syntax... ||r1c1|r1c2%%% #item1 %%% #item2 %%% #item3 r2c1|r2c2|| ||r1c1|r1c2%%% * item1 %%% * item2 %%% * item3 r2c1|r2c2|| ||r1c1|r1c2%%%* item1 %%% * item2 %%% * item3 r2c1|r2c2|| !!Creating advanced tables Would be nice to not have to resort to HTML when doing tables where you want to span columns or rows. Adding colspan/rowspan options and possibly also allowing individual cell alignment (vert and horiz) would be great. Even if this was relegated to something like FANCYTABLES, I'd be happy with it. !!!SPLIT plugin work-around Would have to edit the plugin and/or CSS if you want a border, though. {SPLIT(joincols=>n],fixedsize=>y,colsize=>100|100)} r1c1 --- r1c2 #item1 #item2 #item3 @@@ r2c1 --- r2c2 {SPLIT} !!Numbered lists which continue after some line breaks {CODE(caption="Code",wrap="1")} # ((tw:Top-10 files)) # ((tw:Participate|Top-10 ways to help)) # ((tw:Top-10 news|Top-10 ways to get news)) # ((tw:Top-10 stats)) about Tiki # ((tw:Top-10 differences|Top-10 ways in which Tiki is very different from other projects)) # ((tw:WhyUseTiki|Top-10 reasons to choose Tiki)) # ((tw:Top-10 criticisms))%%% %%% Also,%%% %%% # ((tw:TikiBackronym|Top-10 potential meanings for T-i-k-i)) # ((tw:Top-10 Words)) {CODE} generates: # ((tw:Top-10 files)) # ((tw:Participate|Top-10 ways to help)) # ((tw:Top-10 news|Top-10 ways to get news)) # ((tw:Top-10 stats)) about Tiki # ((tw:Top-10 differences|Top-10 ways in which Tiki is very different from other projects)) # ((tw:WhyUseTiki|Top-10 reasons to choose Tiki)) # ((tw:Top-10 criticisms))%%% %%% Also,%%% %%% # ((tw:TikiBackronym|Top-10 potential meanings for T-i-k-i)) # ((tw:Top-10 Words)) !!!Using + for item continuation An alternative is to use __+__ to continue numbering: {CODE(caption="Code",wrap="1")} # Item # Item # Item + Also, # Item # Item {CODE} generates: # Item # Item # Item + Also, # Item # Item !!Using = with underline === is the syntax for underline. This doesn't work: {CODE(caption="Code",wrap="1")} === 1+1 = 3 === {CODE} workaround number 1 {CODE(caption="Code",wrap="1")} === 1+1 ~61~ 3 === {CODE} generates: === 1+1 ~61~ 3 === workaround number 2 {CODE(caption="Code",wrap="1")} {TAG(tag=u)}1+1 = 3{TAG} {CODE} generates: {TAG(tag=u)}1+1 = 3{TAG} !!Allowing Formatting characters to span paragraphs When you use ~np~::~/np~ or ~np~''~/np~ or similar formatting tags, at leat in 1.9 (haven't tried in 1.10) they don't get recognized. Instead you see the beginning characters, then the paragraph, then the paragraph space, then the continuation of the next paragraph ending with the closing characters. ''This doesn't work properly.'' ''But this does.'' ::Irritating when you want to center text across multiple lines without bracketing:: ::every line with ~np~::~/np~:: ::__''kerrnel22'' learns%%%something new every day!%%%Thanks ricks!__:: !!!Use ~np~%%%~/np~ to break lines within formatting For example: ''This does%%%work properly.'' ::Not so irritating when you want to center%%%text across multiple lines without bracketing%%%every line with ~np~::~/np~:: !!Wrap code Sections to Fit the Window Not sure if this is something browser-specific or Tiki-specific (I think it's both), but when you put really long lines inside CODE blocks they tend to run off the right side of the page and completely mess up the pagescape. It would be nice, based on the size of the window (and therefore the size of the middle content box) to wrap the CODE text at the right margin of the middle box. Having said that, when using CODE blocks on a printer-friendly page, they don't get wrapped there, even when you send it to the printer. I think that's a browser issue. But we should be able to address the wiki page issue? __Solution is easy: use wrap=1 parameter in CODE plugin__ -=Liens utiles=- # Pour en savoir davantage sur la syntaxe de base ** ((Mise en forme du texte)) ~tc~ (alias(Advanced Wiki-syntax,fr)) ~/tc~
Related content
