Список стилей: различия между версиями

Материал из SS220 Paradise Wiki (SS13)
Перейти к навигации Перейти к поиску
Нет описания правки
Нет описания правки
 
Строка 4: Строка 4:
Это страница со стилями которые вы можете использовать в тэгах нашей вики, сейчас она на английском, содержит огромное количество ненужной и не работающей информации и просто плохо выглядит. Но свою цель она выполняет уже сейчас, тут действительно есть некоторые рабочие стили которые нигде в другом месте не указаны, рекомендую зайти в режим редактирования кода и читать от туда.
Это страница со стилями которые вы можете использовать в тэгах нашей вики, сейчас она на английском, содержит огромное количество ненужной и не работающей информации и просто плохо выглядит. Но свою цель она выполняет уже сейчас, тут действительно есть некоторые рабочие стили которые нигде в другом месте не указаны, рекомендую зайти в режим редактирования кода и читать от туда.
Начинать изменения стоит с добавления тэга <nowiki><pre></nowiki> в столб "выдаёт", а после удалить все не рабочие шаблоны.
Начинать изменения стоит с добавления тэга <nowiki><pre></nowiki> в столб "выдаёт", а после удалить все не рабочие шаблоны.
== text formatting markup ==


{| class="wikitable"
2.2. Text Formatting
!  Description
2.2.1. Assorted
! Width=40% |  пишите
Paragraphs
! Width=40% |  выдаёт
Blank lines separate paragraphs.
|-
Strong emphasis
! Colspan="3" style="background: #abe" |  character (inline) formatting  ''applies anywhere''
[+example text+]
|-
Very strong emphasis
|  italic text
[++example text++]
| '' italic''
Hilighted text
 
##example text##
|
Notes
'' italic''
[example text]
|-
Reversed background color text
|  bold text
[rev example text]
| ''' bold'''
Red text
 
{r}example text{/r} or <r>example text</r>
|
Green text
''' bold'''
{g}example text{/g} or <g>example text</g>
|-
Blue text
|  bold and italic
{b}example text{/b} or <b>example text</b>
| ''''' bold &amp; italic'''''
Colored text
 
{#FFFFFF}example text{/#}
|
Justified text
''''' bold &amp; italic'''''
<>( example )
{{table-anchorrow|colspan=3|nowiki||.3cnowiki.3e}}
Argument against: it's should be more about content than about presentation and looks
|-
2.2.2. Citations
|  escape wiki markup
??source??
| {{#tag:syntaxhighlight|
"quote (source)" or 'quote (source)'
 
"quote [source]" or 'quote [source]'
{{^(}}nowiki{{)^}} no [[wiki]] ''markup''{{^(}}/nowiki{{)^}}
2.2.3. Emphasis (italics)
| lang = "html"
Inline
}}
/emphasized words/
|
//emphasized words
no [[wiki]] ''markup''
//emphasized words//
|-
Argument for:
! Colspan="3" style="background: #abe" |  section formatting  ''only at the beginning of the line''
Intuitive. Looks like italics.
|-
''emphasized words''
|  section headings of different levels
Argument for:
|
A natural translation from print, where double-quote means italics. (I added a Gutenberg text to a wiki that uses this, and it naturally italicized where it should have because of this.)
== level 2 ==
^emphasized words^
 
_emphasized words_
=== level 3 ===
Argument for:
 
Established popular "markup" in text-only environments
==== level 4 ====
Argument against:
 
Ambiguity with computer hostnames and URLs which use underscores
===== level 5 =====
These should be quoted anyways
 
~~emphasized words~~
====== level 6 ======
{I}italicized text
 
///emphasized words///
 
Argument against:
----
Too much mark-up.
{{note|1=
Block
*  [], it is page name level.
[/italicized text/]
*  do not put any text on the same line after the ending equal signs.
[i italicized text]
*  an article with 4 or more headings automatically creates a [[wikipedia:help:section#table of contents (toc)|table of contents]] (unless setting the magic word __notoc__).
2.2.4. Bold
}}
Inline
|
*bold text*
 
**bold text**
 
Argument for:
 
Established popular "markup" in text-only environments
level 2
Argument against:
 
Ambiguous with established bulleting method
 
##bold text##
level 3
||bold text||
 
__bold text__
 
{B}bold text
level 4
'''bold text'''
 
Argument against:
 
Multiple single quotes can look like double quote characters in proportional fonts.
level 5
Too much mark-up.
 
Too similar to italic, and far too much markup when combining italic with bold.
 
Block
level 6
[*bold text*]
 
[b bold text]
|-
2.2.5. Inserted Text (underline)
|  horizontal rule
Inline
|  text before
_underline_
----
__underline__
text after
++underline++
 
Block
|
[_underline_]
text before
2.2.6. Deleted Text (strikethrough)
----
Inline
text after
-strikethough-
|-
--strikethough--
|  bullet list
Argument against: unacceptable because hyphens are far too common - both single hyphens representing minus signs and double hyphens representing em-dashes.
|
Block
 
[-strikethrough-]
 
-/strikethrough/-
* start each line
2.2.7. Monospaced Text
* with an [[wikipedia:asterisk|asterisk]] (*).
Inline
** more asterisks give deeper
=technical term=
*** and deeper levels.
Argument against: could conceivably cause some problem with mathematics.
* line breaks don't break levels.
@technical term@
*** but jumping levels creates empty space.
@@technical term@@
Any other start ends the list.
#technical term#
 
##technical term##
 
Argument for: `#` is often a comment character, and you don't put comments in inline code snippets.
* combine bullet list
`technical term`
** with definition
Argument against: backticks are hard to read in many fonts and can be mangled by typesetting software.
::- definition
'technical term'
** creates empty space
Argument against: unacceptable because single quotes are too common.
 
Block
 
[=technical term=]
* combine bullet list
{{technical term}}
** with definition
/*technical term*/
*:- definition
2.2.8. Literal/Unprocessed Text
** without empty spaces
Inline
 
%%example text%%
 
`example text`
*bullet list
``example text``
:- definition
Argument against: backticks are hard to read in many fonts and can be mangled by typesetting software.
:* sublist that doesn't create empty
```example text```
:* spaces after definition
Argument against:
 
Backticks are hard to read in many fonts and can be mangled by typesetting software.
 
Too much mark-up.
|
Block
 
{example text}
 
{{{example text}}}
* start each line
Argument against:
* with an [[wikipedia:asterisk|asterisk]] (*).
Too much mark-up.
** more asterisks give deeper
[%example text%]
*** and deeper levels.
[\example text\]
* line breaks don't break levels.
[=example text=]
*** but jumping levels creates empty space.
[esc]example text[/esc]
Any other start ends the list.
[literal]example text[/esc]
 
Argument against:
 
No benefit over SGML/XML.
* combine bullet list
SGML/XML Markup
** with definition
<nowiki>example text</nowiki>
::- definition
<verbatim>example text</verbatim>
** creates empty space
<ignore>example text</ignore>
 
<literal>example text</literal>
 
2.2.9. Superscript Text
* combine bullet list
Inline
** with definition
^superscript text^
*:- definition
^^superscript text^^
** without empty spaces
Block
 
[^superscript text^]
 
2.2.10. Subscript Text
*bullet list
Inline
:- definition
,,subscript text,,
:* sublist that doesn't create empty
~subscript text~
:* spaces after definition
vvsubscript textvv
 
Argument against: the name of the wiki that has this syntax has been witheld to avoid humiliating the author.
|-
Block
|  numbered list
[,subscript text,]
|
2.2.11. Large Text
 
Inline
 
+large text+
# start each line
Argument against: could conceivably cause problems with mathematics.
# with a [[wikipedia:number_sign|number sign]] (#).
Block
## more number signs give deeper
[+large text+]
### and deeper
~+small text+~!
### levels.
2.2.12. Small Text
# line breaks don't break levels.
Inline
### but jumping levels creates empty space.
-small text-
# blank lines
Argument against: unacceptable because single hyphens are too common.
 
Block
 
[-small text-]
# end the list and start another.
!-small text-!
Any other start also
~-small text-~
ends the list.
2.2.13. Centered Text
 
Inline
 
{c}example text
# use "nowiki" tags to display a literal (#) at the beginning of a line without interpreting it as a numbered list.
<:>example text
 
Block
 
>>example text<<
|
><( example text )
 
2.2.14. Left Aligned Text
 
{l}example text
# start each line
<(>example text
# with a [[wikipedia:number_sign|number sign]] (#).
Block
## more number signs give deeper
<-( example text )
### and deeper
2.2.15. Right Aligned Text
### levels.
{r}example text
# line breaks don't break levels.
<)>example text
### but jumping levels creates empty space.
Block
# blank lines
->( example text )
 
2.3. Line Breaks
 
%%%%
# end the list and start another.
>>>
Any other start also
\\
ends the list.
[[BR]]
 
Argument against:
 
No benefit over HTML.
# use "nowiki" tags to display a literal (#) at the beginning of a line without interpreting it as a numbered list.
Locale-specific.
{{table-anchorrow|colspan=3|definition list}}
Obsfuscated abbreviation.
|-
2.4. Headings
|  definition list
Method 1
|
A sequence of heading characters at the beginning of a line indicates heading level.
 
= Heading 1
;item 1
== Heading 2
: definition 1
=== Heading 3
;item 2
Argument against
: definition 2-1
Less important titles stand out more.
: definition 2-2
! Heading 1
 
!! Heading 2
 
!!! Heading 3
{{note|1= at the end of the line, if the line begins with a semicolon (;), any inserted colon (:) will not be displayed.  If you want for the colon to be displayed, escape it by writing :.}}
Argument for
|
Intuitive. Exclamation point says: here's something important.
 
Argument against
 
Less important titles stand out more.
;item 1
- Heading 1
: definition 1
-- Heading 2
;item 2
--- Heading 3
: definition 2-1
Argument against
: definition 2-2
Less important titles stand out more.
 
Argument against
|-
Double hyphens at the beginning of a line may also introduce a signature.
|  indent text
Method 2
|
A sequence of heading characters at the beginning and end of a line indicates heading level.
 
= Heading 1 =
: single indent
== Heading 2 ==
:: double indent
=== Heading 3 ===
::::: multiple indent
Argument for
 
Intuitive. Looks like a banner.
 
Argument against
----
Less important titles stand out more.
{{note|1= this workaround may harm accessibility.}}
-= Heading 1 =-
|
-== Heading 2 ==-
 
-=== Heading 3 ===-
 
Argument against
: single indent
Forces user to count the correct number of characters twice.
:: double indent
Argument against
::::: multiple indent
Less important titles stand out more.
 
Method 3
|-
Rule: a sequence of heading characters at the beginning of a line indicates heading level, and any heading characters after the title are ignored.
|  mixture of different types of list
= Heading 1 =======================================
|
== Heading 2 ===================
 
=== Heading 3 ===
 
Basically the number of heading characters at the end is ignored, as long as there is at least one.
# one
# two
#* two point one
#* two point two
# three
#; three item one
#: three def one
# four
#: four def one
#: this looks like a continuation
#: and is often used
#: instead  of
# five
## five sub 1
### five sub 1 sub 1
## five sub 2
 
 
----
{{note|1= the usage of #: and *: for breaking a line within an item may also harm accessibility.}}
|
 
 
# one
# two
#* two point one
#* two point two
# three
#; three item one
#: three def one
# four
#: four def one
#: this looks like a continuation
#: and is often used
#: instead  of
# five
## five sub 1
### five sub 1 sub 1
## five sub 2
 
|-
|  preformatted text
|  start each line with a space.
  Text is '''preformatted''' and
  ''markups'' '''''can''''' be done.
 
----
{{note|1= this way of preformatting only applies to section formatting. Character formatting markups are still effective.}}
|
  start each line with a space.
  Text is '''preformatted''' and
  ''markups'' '''''can''''' be done.
|-
|  preformatted text blocks
| 
start with a space in the first column,
(before the ).
 
 
Then your block format will be
    maintained.
 
 
This is good for copying in code blocks:
 
 
def function():
    """ documentation string"""
 
    if true:
        print true
    else:
        print false
 
|
{{#tag:nowiki|
start with a space in the first column,
(before the ).
 
 
Then your block format will be
    maintained.
 
 
This is good for copying in code blocks:
 
 
def function():
    """ documentation string"""
 
    if true:
        print true
    else:
        print false
}}
|}
 
{{anchor||.3cp.3e}}
 
== paragraphs ==
 
{{anchor||.3cbr.3e}}
 
 
mediawiki ignores single line breaks. To start a new paragraph, leave an empty line. You can force a line break within a paragraph with the html tag {{tag|br|single}}.
 
== html tags ==
 
{{anchor||.3cdiv.3e||.3cspan.3e}}
 
 
some [[wikipedia:html|html]] tags are allowed in mediawiki, for example {{tag|code|open}}, [[w:div and span|{{tag|div|open}}, and {{tag|span|open}}]]. These apply anywhere you insert them.
 
{| class="wikitable"
!  Description
! Width=40% |  you type
! Width=40% |  you get
{{table-anchorrow|colspan=3||.3cins.3e||.3cu.3e}}
|-
|  inserted (displays as underline in most browsers)
|
inserted
 
or
 
underline
 
|
inserted
 
or
 
underline
{{table-anchorrow|colspan=3||.3cdel.3e||.3cs.3e}}
|-
|  deleted (displays as strike-through in most browsers)
|
strike-through
 
or
 
deleted
 
 
|
strike-through
 
or
 
deleted
{{table-anchorrow|colspan=3||.3ccode.3e}}
|-
|  fixed width text
|  source code
|  source code
{{table-anchorrow|colspan=3||.3cblockquote.3e}}
|-
|  blockquotes
|
text before
blockquote
text after
 
{{note|1= if the quote contains multiple paragraphs the tags need to be on separate lines to display properly, i.e.:
 
 
first paragraph.
 
Second paragraph.
 
 
{{tracked|t309778|float=none}}
}}
|
text before
blockquote
text after
{{table-anchorrow|colspan=3||.3cq.3e}}
|-
|  quotes
|  this is a quotation
{{note|1= the q element '''must not''' be used in place of quotation marks that do not represent quotes; for example, it is inappropriate to use the q element for marking up sarcastic statements.[ html living standardthe &lt;'''q'''&gt; element]}}
|  this is a quotation
|-
|  comment
|
 
 
 
comments are visible only
in the edit zone.
 
 
|
 
 
 
comments are visible only
in the edit zone.
 
{{table-anchorrow|colspan=3||.3cpre.3e}}
|-
|  completely preformatted text
|
 
 
text is '''preformatted''' and
''markups'' '''''cannot''''' be done
 
 
 
----
{{note|1= for marking up of preformatted text, check the "preformatted text" entry at the end of the previous table.}}
|
 
 
text is '''preformatted''' and
''markups'' '''''cannot''''' be done
 
 
|-
|  '''customized''' preformatted text
|
 
 
text is '''preformatted'''
with a style and
''markups'' '''''cannot''''' be done
 
 
 
----
{{note|1= a css style can be named within the style attribute.}}
|
 
 
text is '''preformatted'''
with a style and
''markups'' '''''cannot''''' be done
 
 
|}


Argument against
While more important titles may stand out, they don't have to. It would be nice if this rule was enforced.
Method 4
Rule: a line of text with all-capitalized words.
Any Line Of All Capitalized Words Becomes A Heading
Argument for
Clever.
Argument against
Actual titles don't have all capitalized words.
Argument against
Not feasible for most non-English languages.
Method 5
Rule: headings are underlined (or over-and underlined) with a printing nonalphanumeric character. The underline/overline must be at least as long as the title text.
=============
First Heading
=============
Second Heading
21:26, 6 июня 2022 (MSK)21:26, 6 июня 2022 (MSK)[[Участник:Noobiant 69|Noobiant 69]] ([[Обсуждение участника:Noobiant 69|обсуждение]]) 21:26, 6 июня 2022 (MSK)
Third Heading
-------------
Argument pro
Important titles stand out more.
Argument against
Hard to use with proportional fonts. A possible fix is to just require a minimum amount of underlining (eg. four characters).
Method 6
Rule: heading characters plus a number indicate heading level.
---+1 Heading 1
---+2 Heading 2
---+3 Heading 3
Method 7
Rule: heading characters plus additional sequence of characters to indicate heading level.


continued:
---+ Heading 1
{| class="wikitable" | style="table-layout: fixed; width: 100%"
---++ Heading 2
!  Description
---+++ Heading 3
! Width=40% |  you type
Argument against
! Width=40% |  you get
:Too much markup.
|-
Argument pro
|  '''default''' preformatted text has a css attribute (white-space: pre-wrap;) to wrap the text according to available width
Less important titles stand out more.
|
Method 8
this long sentence is used to demonstrate text wrapping. This additional sentence makes the text even longer. This additional sentence makes the text even longer.
Rule: Change of bullet character indicates change of level


* Heading 1 *
+ Heading 2 +
* Heading 1 *
- Heading 2 -
+ Heading 3 +
Method 9
Rule: Number of heading characters indicates level importance. The highest number of heading characters is heading 1, the second highest is heading 2, etc.


|
==== Heading 1
this long sentence is used to demonstrate text wrapping. This additional sentence makes the text even longer. This additional sentence makes the text even longer.
=== Heading 2
== Heading 3
= Heading 4
Argument pro
Important titles stand out more.
Argument against
There must be a maximum number of levels.
Miscellaneous
= # enumerated heading text =
2.5. Lists and Indentations
2.5.1. Known Bullet Characters
*
-
@
+
!
?
>
%
#
o
Argument against:
The letter 'o' is a word in many languages.
x
2.5.2. Unordered Lists
Method 1
Rule: a sequence of bullet characters indicate level.


|-
* level 1
|  '''customized''' preformatted text with '''disabled''' text wrapping
** level 2
|
*** level 3
this long sentence is used to demonstrate text wrapping. This additional sentence makes the text even longer. This additional sentence makes the text even longer.
000 also aligned with third level, but no bullet
... also aligned with third level, but no bullet
Argument for
easier to parse.
Argument against
less intuitive.
Method 2
Rule: a sequence of spaces followed by a bullet character indicate level.


* level 1
* level 2
  * level 3
    * level 5
Argument against
Counting spaces, like other invisible characters, is not user friendly.
Method 2
Rule: an indent followed by a bullet character indicate level.


|
* level 1
this long sentence is used to demonstrate text wrapping. This additional sentence makes the text even longer. This additional sentence makes the text even longer.


|}
    * level 2
            * level 3
            * level 4
Method 3
Rule: A change of bullet character indicates level change. Indetation optional.


* level 1
- level 2
+ level 3
- level 2 again
@ level 3
+ level 4
2.5.3. Ordered Lists
Method 1
Rule: a sequence of ordered list characters indicate level.
# level 1
## level 2
### level 3
#3 restart numbering from 3
> level 1
>> level 2
>>> level 3
0 level 1
00 level 2
000 level 3
Method 2
Rule: a sequence of spaces followed by an enumerator indicate level.
1. level 1
1. level 2
  1. level 3
1.#3 restart numbering from 3
1) level 1
2) level 2
  3) level 3
Method 3
Rule: Each level has it's own numeration.
1. level 1
1.1 level 2
1.1.1 level 3
1.2 level 2
2.5.4. Indentations / Block Quotes
Method 1
Rule: a sequence of spaces indicates indentation level.


 
outer
== inserting symbols ==
indent 1
 
  indent 2
 
Method 2
symbols and other special characters not available on your keyboard can be inserted in a multitude of ways. Many [ operating systems and browsers] allow you to insert special characters through a menu option or operating system panel. Additionally, you can use the wikieditor or [[visualeditor/special characters|visualeditor]] to insert them into the edit screen.
Rule: a sequence of indentation characters indicates indentation level.
 
outer
 
: indent 1
As a last resort, you can use a special sequence of characters. Those sequences are called html entities. For example, the following sequence (entity) '''''' when inserted will be shown as right arrow html symbol  and '''''' when inserted will be shown as an em dash html symbol .
:: indent 2
----
outer
{{note|1= hover over any symbol to reveal the entity that produces it.  Some symbols not available in the current font will appear as empty squares.}}
> indent 1
 
>> indent 2
{| class="wikitable" style="width:100%; text-align:center; font-weight:bold;"
Argument for: commonly used when pretty-printing e-mails and news posts.
|+  html symbol entities
2.5.5. Definition Lists
|-
Method 1
| a
;Term: Definition
| a
  $ Term: Definition
| a
Method 2
| a
Term:: Definition
| 
Method 3
|
Term:
|
    Definition
| a
2.6. Tables
| a
Method 1: Sequence of Rows
|
| col1 | col2 | col3 |
|
|| col1 || col2 || col3 ||
|
Method 2
| &amp;
[| col 1, row 1 || col 2, row 1 ||
|
|| col 1, row 2 || col 2, row 2 |]
|
Method 3: Drawing Boxes
| a
+------------+------------+-----------+
| a
| Header 1  | Header 2  | Header 3  |
|
+============+============+===========+
| a
| body row 1 | column 2  | column 3 |
| a
+------------+------------+-----------+
| a
| body row 2 | Cells may span columns.|
| a
+------------+------------+-----------+
|  
| body row 3 | Cells may | - Cells  |
|  
+------------+ span rows. | - contain |
|  
| body row 4 |           | - blocks. |
|  
+------------+------------+-----------+
|  
Argument against
|  
Very hard to parse and takes a lot of effort to type.
| c
|---------------------|
| c
| Header 1 | Header 2 |
|
|=====================|
|  
| Column 1 | Column 2 |
|-
|---------------------|
|
Method 4
|  
=====  ===== ======
|  
  Inputs    Output
|  
------------ ------
|  
  A      B    A or B
|  
=====  =====  ======
|  
False  False  False
|  
True  False  True
|  
False  True  True
|  
True  True  True
|  
=====  ===== ======
|
Method 5: Definition Tables
|
Term 1 |
|  
  Definition 1 begins here.
|  
  Term 1.1 |
|  
      Definition 1.1
|  
  Term 1.2 |
|
      Definition 1.2
| e
  This is part of definition 1.
| e
Term 2 |
| e
  Here's definition 2.
| e
Method 6: Wiki-pipe Syntax
| e
{|
| e
!heading 1 !! heading2
|
!heading 3
|   
|
|
|
|
|
|
|-
|  
|
| e
| e
|
|
|
|
| 12
| 14
| 34
|
|
|
|
| &gt;
|
|
|
| ...
| i
| i
| i
| i
|
| i
| i
| i
|
|
|
|
|-
|  
|
| i
| i
|
|
|
|
|
|
|
|
|
| "
|
|
|
|
|
|
| '
| &lt;
|   
|  
|  
|  
|  
|  
|  
|  
| &nbsp;
|
|-
| =
|
|
|
|
| n
| n
|
|
| o
| o
| o
| o
|
|
| o
| o
| 
|
|
|
|
|
|
| a
| o
|
|
| o
| o
|
| o
|-
| o
|
|
|
|
|
|
|
|
|
|
|
| '
| "
|
|
|
|
| "
|
|
|
|
|
|
| "
| r
|
|
|
|
|
|-
|  
| '
|  
| s
| s
|
|
|
|
|
|
|
|
|
|
|
|  
| 1
| 2
| 3
|  
|  
|
|
|
|
|
|
|  
|
|
|  
|-
|
| tm
| u
| u
|
|
| u
| u
| u
| u
|  
|
|  
|
| u
| u
|  
|
|
| y
| y
|
| y
| y
|
|
|
|
|}
 
{| class="wikitable"
! Description
! Width=40% |  you type
! Width=40% |  you get
|-
|  copyright symbol
|class=mw-code|
|
:::''''''
|-
|-
| greek delta letter symbol
|text 1a || text 2a || text 3a
|class=mw-code|
|
:::''''''
|-
|-
| euro currency symbol
|text 1b
|class=mw-code|
|text 2b
|
|text 3b
:::''''''
|}
|}
 
Method 7: Relational
 
[[Table][Seperator=;]
see the list of all html entities on the wikipedia article [[wikipedia:list of html entities|list of html entities]]. Additionally, mediawiki supports two non-standard entity reference sequences: &amp;; and &amp;; which are both considered equivalent to  which is a [[wikipedia:right-to-left mark|right-to-left mark]]. (used when combining right to left languages with left to right languages in the same page.)
[Columns=Person,Height,Weight]
 
Person=Person; Height=Height; Weight=Weight
== html tags and symbol entities displayed themselves (with and without interpreting them) ==
Person=Peter; Height=180; Weight=84
 
Person=Martha; Weight=52; Height=167
: &nbsp; ''''''
]
 
2.6.1. Cell Attributes
: typo to be corrected &nbsp; ''' typo to be corrected'''
Cell Attribute Specification
 
|abc
: typo to be corrected &nbsp; ''' typo to be corrected'''
||<abc>
 
||{a,b=c}
 
Cell Attributes in Use
=== nowiki for html ===
Top alignment
 
{t} or <^>
{{tag|nowiki|s}}  can prohibit (html) tags:
Bottom alignment
*  &nbsp;  but ''not'' &amp; symbol escapes:
{b} or <v>
* &amp; &nbsp; &amp;
Column spanning
 
{w=number} or <-number>
 
Row spanning
to print &amp; symbol escapes as text, use "&amp;" to replace the "&amp;" character (eg. Type "&nbsp;", which results in "&nbsp;").
<|number>
 
Border width
== other formatting ==
{Tb=number}
 
Cell class
 
{C=string}
beyond the text formatting markup shown hereinbefore, here are some other formatting references:
Cell style
 
{s=string}
 
Cell width
* {{ll|help:links|nsp=0}}
<100%>
* {{ll|help:lists|nsp=0}}
Background color
* {{ll|help:images|nsp=0}}
<#XXXXXX>
 
Miscellaneous
 
|<<END|<<END|
* languageconverter markup  see {{ll|writing systems/syntax}}
col1 text is here
 
END
 
col2 text is here
* references  see {{ll|extension:cite}}
END
* []
2.7. Horizontal Rules/Separators
 
---
 
---- (4 dashes at beginning of line--extra dashes are ignored.)
you can find more references at {{ll|help:contents}}.
-----
 
____ (4 underscores at beginning of line)
== references ==
---- (4 dashes at beginning of line--more than 4 gets thicker.)
 
Argument against:
 
This seems like a petty stylistic feature which I can't imagine someone actually caring about.
 
Discussion
[[category:help{{#translation:}}|formatting]]
Having four as a minimum is totally arbitrary. Parsing is not ambiguous as a separator should begin and end with a newline. Thus the only possible ambiguity is for the reader in that a small separator could get "lost" in the document. -- IanBollinger?
One and two could not be the minimum for obvious reasons. Three cannot for I've seen at least one Wiki that uses --- for an em dash, and some word processors do as well. So four hyphens is the minimum number that can safely be chosen.
2.8. Meta-Wiki
2.8.1. Macros, Variables, Plugins and Extensions
[[MacroName(arguments)]]
<MacroName>
<MacroName(arguments)>
@MacroName@
{{MacroName(arguments)}}
%MacroName{"parameter" key="named parameter"}%
<?plugin MacroName arg1=val1 arg2=val2 ?>
[[MacroName][parameter=value]...body...]
$MacroName
2.8.2. Comments
#comment
##comment
SGML/XML Markup
<hide>comment</hide>
2.8.3. Processing Instructions and Meta Data
#TYPE value
@type:name:value
%META:type{arg1="val1" arg2="val2"}%
2.9. Character Replacement
-- becomes an em-dash. (—)
1-1 becomes an en-dash. (1–1)
"text becomes a double left quote. (“text)
text" becomes a double right quote. (text”)
'text becomes a single left quote. (‘text)
** Argument against: some English abbreviations begin with single right quotes ("I said 'e would").
don't becomes a single right quote. (don’t)
text' becomes a single right quote. (text’)
' becomes &apos; in XML.
> becomes &gt; in SGML/XML.
< becomes &lt; in SGML/XML.
& becomes &amp; in SGML/XML.
ff, fi, fl, ffi, ffl and st become their appropriate ligatures.

Текущая версия от 18:26, 6 июня 2022

MakeshiftGarrote.PNGЭтой странице требуется переводMakeshiftGarrote.PNG
Эта статья содержит непереведенную информацию.


Newscaster.pngЭта страница должна быть пересмотрена/обновленаNewscaster.png
Эта статья содержит устаревшие данные, необходимо сверить и обновить информацию.
Причина: Много нерабочей и не нужной информации, не отформатировано


Это страница со стилями которые вы можете использовать в тэгах нашей вики, сейчас она на английском, содержит огромное количество ненужной и не работающей информации и просто плохо выглядит. Но свою цель она выполняет уже сейчас, тут действительно есть некоторые рабочие стили которые нигде в другом месте не указаны, рекомендую зайти в режим редактирования кода и читать от туда. Начинать изменения стоит с добавления тэга <pre> в столб "выдаёт", а после удалить все не рабочие шаблоны.

2.2. Text Formatting 2.2.1. Assorted Paragraphs Blank lines separate paragraphs. Strong emphasis [+example text+] Very strong emphasis [++example text++] Hilighted text

    1. example text##

Notes [example text] Reversed background color text [rev example text] Red text {r}example text{/r} or <r>example text</r> Green text {g}example text{/g} or <g>example text</g> Blue text {b}example text{/b} or example text Colored text {#FFFFFF}example text{/#} Justified text <>( example ) Argument against: it's should be more about content than about presentation and looks 2.2.2. Citations ??source?? "quote (source)" or 'quote (source)' "quote [source]" or 'quote [source]' 2.2.3. Emphasis (italics) Inline /emphasized words/ //emphasized words //emphasized words// Argument for: Intuitive. Looks like italics. emphasized words Argument for: A natural translation from print, where double-quote means italics. (I added a Gutenberg text to a wiki that uses this, and it naturally italicized where it should have because of this.) ^emphasized words^ _emphasized words_ Argument for: Established popular "markup" in text-only environments Argument against: Ambiguity with computer hostnames and URLs which use underscores These should be quoted anyways ~~emphasized words~~ {I}italicized text ///emphasized words/// Argument against: Too much mark-up. Block [/italicized text/] [i italicized text] 2.2.4. Bold Inline

  • bold text*
    • bold text**

Argument for: Established popular "markup" in text-only environments Argument against: Ambiguous with established bulleting method

    1. bold text##

||bold text|| __bold text__ {B}bold text bold text Argument against: Multiple single quotes can look like double quote characters in proportional fonts. Too much mark-up. Too similar to italic, and far too much markup when combining italic with bold. Block [*bold text*] [b bold text] 2.2.5. Inserted Text (underline) Inline _underline_ __underline__ ++underline++ Block [_underline_] 2.2.6. Deleted Text (strikethrough) Inline -strikethough- --strikethough-- Argument against: unacceptable because hyphens are far too common - both single hyphens representing minus signs and double hyphens representing em-dashes. Block [-strikethrough-] -/strikethrough/- 2.2.7. Monospaced Text Inline

technical term

Argument against: could conceivably cause some problem with mathematics. @technical term@ @@technical term@@

  1. technical term#
    1. technical term##

Argument for: `#` is often a comment character, and you don't put comments in inline code snippets. `technical term` Argument against: backticks are hard to read in many fonts and can be mangled by typesetting software. 'technical term' Argument against: unacceptable because single quotes are too common. Block [=technical term=] Шаблон:Technical term /*technical term*/ 2.2.8. Literal/Unprocessed Text Inline %%example text%% `example text` ``example text`` Argument against: backticks are hard to read in many fonts and can be mangled by typesetting software. ```example text``` Argument against: Backticks are hard to read in many fonts and can be mangled by typesetting software. Too much mark-up. Block {example text} {{{example text}}} Argument against: Too much mark-up. [%example text%] [\example text\] [=example text=] [esc]example text[/esc] [literal]example text[/esc] Argument against: No benefit over SGML/XML. SGML/XML Markup example text <verbatim>example text</verbatim> <ignore>example text</ignore> <literal>example text</literal> 2.2.9. Superscript Text Inline ^superscript text^ ^^superscript text^^ Block [^superscript text^] 2.2.10. Subscript Text Inline ,,subscript text,, ~subscript text~ vvsubscript textvv Argument against: the name of the wiki that has this syntax has been witheld to avoid humiliating the author. Block [,subscript text,] 2.2.11. Large Text Inline +large text+ Argument against: could conceivably cause problems with mathematics. Block [+large text+] ~+small text+~! 2.2.12. Small Text Inline -small text- Argument against: unacceptable because single hyphens are too common. Block [-small text-] !-small text-! ~-small text-~ 2.2.13. Centered Text Inline {c}example text <:>example text Block >>example text<< ><( example text ) 2.2.14. Left Aligned Text {l}example text <(>example text Block <-( example text ) 2.2.15. Right Aligned Text {r}example text <)>example text Block ->( example text ) 2.3. Line Breaks %%%% >>> \\ BR Argument against: No benefit over HTML. Locale-specific. Obsfuscated abbreviation. 2.4. Headings Method 1 A sequence of heading characters at the beginning of a line indicates heading level. = Heading 1 == Heading 2 === Heading 3 Argument against Less important titles stand out more. ! Heading 1 !! Heading 2 !!! Heading 3 Argument for Intuitive. Exclamation point says: here's something important. Argument against Less important titles stand out more. - Heading 1 -- Heading 2 --- Heading 3 Argument against Less important titles stand out more. Argument against Double hyphens at the beginning of a line may also introduce a signature. Method 2 A sequence of heading characters at the beginning and end of a line indicates heading level.

Heading 1

Heading 2

Heading 3

Argument for Intuitive. Looks like a banner. Argument against Less important titles stand out more. -= Heading 1 =- -== Heading 2 ==- -=== Heading 3 ===- Argument against Forces user to count the correct number of characters twice. Argument against Less important titles stand out more. Method 3 Rule: a sequence of heading characters at the beginning of a line indicates heading level, and any heading characters after the title are ignored.

Heading 1 ======================================

Heading 2 =================

Heading 3

Basically the number of heading characters at the end is ignored, as long as there is at least one.

Argument against While more important titles may stand out, they don't have to. It would be nice if this rule was enforced. Method 4 Rule: a line of text with all-capitalized words. Any Line Of All Capitalized Words Becomes A Heading Argument for Clever. Argument against Actual titles don't have all capitalized words. Argument against Not feasible for most non-English languages. Method 5 Rule: headings are underlined (or over-and underlined) with a printing nonalphanumeric character. The underline/overline must be at least as long as the title text.

=

First Heading

=

Second Heading 21:26, 6 июня 2022 (MSK)21:26, 6 июня 2022 (MSK)Noobiant 69 (обсуждение) 21:26, 6 июня 2022 (MSK) Third Heading

Argument pro Important titles stand out more. Argument against Hard to use with proportional fonts. A possible fix is to just require a minimum amount of underlining (eg. four characters). Method 6 Rule: heading characters plus a number indicate heading level. ---+1 Heading 1 ---+2 Heading 2 ---+3 Heading 3 Method 7 Rule: heading characters plus additional sequence of characters to indicate heading level.

---+ Heading 1 ---++ Heading 2 ---+++ Heading 3 Argument against

Too much markup.

Argument pro Less important titles stand out more. Method 8 Rule: Change of bullet character indicates change of level

  • Heading 1 *

+ Heading 2 +

  • Heading 1 *

- Heading 2 - + Heading 3 + Method 9 Rule: Number of heading characters indicates level importance. The highest number of heading characters is heading 1, the second highest is heading 2, etc.

==== Heading 1 === Heading 2 == Heading 3 = Heading 4 Argument pro Important titles stand out more. Argument against There must be a maximum number of levels. Miscellaneous

# enumerated heading text

2.5. Lists and Indentations 2.5.1. Known Bullet Characters

- @ + ! ? > %

o Argument against: The letter 'o' is a word in many languages. x 2.5.2. Unordered Lists Method 1 Rule: a sequence of bullet characters indicate level.

  • level 1
    • level 2
      • level 3

000 also aligned with third level, but no bullet ... also aligned with third level, but no bullet Argument for easier to parse. Argument against less intuitive. Method 2 Rule: a sequence of spaces followed by a bullet character indicate level.

  • level 1
* level 2
 * level 3
   * level 5

Argument against Counting spaces, like other invisible characters, is not user friendly. Method 2 Rule: an indent followed by a bullet character indicate level.

  • level 1
    * level 2
           * level 3
            * level 4

Method 3 Rule: A change of bullet character indicates level change. Indetation optional.

  • level 1

- level 2 + level 3 - level 2 again @ level 3 + level 4 2.5.3. Ordered Lists Method 1 Rule: a sequence of ordered list characters indicate level.

  1. level 1
    1. level 2
      1. level 3
  2. 3 restart numbering from 3

> level 1 >> level 2 >>> level 3 0 level 1 00 level 2 000 level 3 Method 2 Rule: a sequence of spaces followed by an enumerator indicate level. 1. level 1 

1. level 2
 1. level 3

1.#3 restart numbering from 3 1) level 1 

2) level 2
 3) level 3

Method 3 Rule: Each level has it's own numeration. 1. level 1 1.1 level 2 1.1.1 level 3 1.2 level 2 2.5.4. Indentations / Block Quotes Method 1 Rule: a sequence of spaces indicates indentation level.

outer 

indent 1
 indent 2

Method 2 Rule: a sequence of indentation characters indicates indentation level. outer

indent 1
indent 2

outer > indent 1 >> indent 2 Argument for: commonly used when pretty-printing e-mails and news posts. 2.5.5. Definition Lists Method 1

Term
Definition
  $ Term: Definition

Method 2 Term:: Definition Method 3 Term: 

   Definition

2.6. Tables Method 1: Sequence of Rows | col1 | col2 | col3 | || col1 || col2 || col3 || Method 2 [| col 1, row 1 || col 2, row 1 || || col 1, row 2 || col 2, row 2 |] Method 3: Drawing Boxes +------------+------------+-----------+ | Header 1 | Header 2 | Header 3 | +============+============+===========+ | body row 1 | column 2 | column 3 | +------------+------------+-----------+ | body row 2 | Cells may span columns.| +------------+------------+-----------+ | body row 3 | Cells may | - Cells | +------------+ span rows. | - contain | | body row 4 | | - blocks. | +------------+------------+-----------+ Argument against Very hard to parse and takes a lot of effort to type. |---------------------| | Header 1 | Header 2 | |=====================| | Column 1 | Column 2 | |---------------------| Method 4

===== =
  Inputs     Output

------ 

 A      B    A or B
===== =

False False False True False True False True True True True True

===== =

Method 5: Definition Tables Term 1 | 

  Definition 1 begins here.
  Term 1.1 |
     Definition 1.1
  Term 1.2 |
     Definition 1.2
  This is part of definition 1.

Term 2 | 

  Here's definition 2.

Method 6: Wiki-pipe Syntax

heading 1 heading2 heading 3
text 1a text 2a text 3a
text 1b text 2b text 3b

Method 7: Relational [[Table][Seperator=;] [Columns=Person,Height,Weight] Person=Person; Height=Height; Weight=Weight Person=Peter; Height=180; Weight=84 Person=Martha; Weight=52; Height=167 ] 2.6.1. Cell Attributes Cell Attribute Specification |abc ||<abc> ||{a,b=c} Cell Attributes in Use Top alignment {t} or <^> Bottom alignment {b} or <v> Column spanning {w=number} or <-number> Row spanning <|number> Border width {Tb=number} Cell class {C=string} Cell style {s=string} Cell width <100%> Background color <#XXXXXX> Miscellaneous |<<END|<<END| col1 text is here END col2 text is here END 2.7. Horizontal Rules/Separators ---

(4 dashes at beginning of line--extra dashes are ignored.)

____ (4 underscores at beginning of line)

(4 dashes at beginning of line--more than 4 gets thicker.)

Argument against: This seems like a petty stylistic feature which I can't imagine someone actually caring about. Discussion Having four as a minimum is totally arbitrary. Parsing is not ambiguous as a separator should begin and end with a newline. Thus the only possible ambiguity is for the reader in that a small separator could get "lost" in the document. -- IanBollinger? One and two could not be the minimum for obvious reasons. Three cannot for I've seen at least one Wiki that uses --- for an em dash, and some word processors do as well. So four hyphens is the minimum number that can safely be chosen. 2.8. Meta-Wiki 2.8.1. Macros, Variables, Plugins and Extensions MacroName(arguments) <MacroName> <MacroName(arguments)> @MacroName@ Шаблон:MacroName(arguments) %MacroName{"parameter" key="named parameter"}% <?plugin MacroName arg1=val1 arg2=val2 ?> [[MacroName][parameter=value]...body...] $MacroName 2.8.2. Comments

  1. comment
    1. comment

SGML/XML Markup <hide>comment</hide> 2.8.3. Processing Instructions and Meta Data

  1. TYPE value

@type:name:value %META:type{arg1="val1" arg2="val2"}% 2.9. Character Replacement -- becomes an em-dash. (—) 1-1 becomes an en-dash. (1–1) "text becomes a double left quote. (“text) text" becomes a double right quote. (text”) 'text becomes a single left quote. (‘text) 

** Argument against: some English abbreviations begin with single right quotes ("I said 'e would").

don't becomes a single right quote. (don’t) text' becomes a single right quote. (text’) ' becomes ' in XML. > becomes > in SGML/XML. < becomes < in SGML/XML. & becomes & in SGML/XML. ff, fi, fl, ffi, ffl and st become their appropriate ligatures.

Источник — https://wiki.ss220.space/index.php?title=Список_стилей&oldid=22046