Skip to content

Commit 149dd4a

Browse files
committed
pyrofork: docs: text-formatting: Move up HTML section
Signed-off-by: wulan17 <wulan17@nusantararom.org>
1 parent 4926eda commit 149dd4a

File tree

1 file changed

+68
-68
lines changed

1 file changed

+68
-68
lines changed

docs/source/topics/text-formatting.rst

Lines changed: 68 additions & 68 deletions
Original file line numberDiff line numberDiff line change
@@ -44,68 +44,6 @@ list of the basic styles currently supported by Pyrofork.
4444
fixed-width
4545
code block
4646

47-
Markdown Style
48-
--------------
49-
50-
.. warning::
51-
52-
The Markdown style is not recommended for complex text formatting.
53-
If you want to use complex text formatting such as nested entities, overlapping entities use the HTML style instead.
54-
55-
56-
To strictly use this mode, pass :obj:`~pyrogram.enums.ParseMode.MARKDOWN` to the *parse_mode* parameter when using
57-
:meth:`~pyrogram.Client.send_message`. Use the following syntax in your message:
58-
59-
.. code-block:: text
60-
61-
**bold**
62-
63-
__italic__
64-
65-
--underline--
66-
67-
~~strike~~
68-
69-
||spoiler||
70-
71-
[text URL](https://pyrogram.org/)
72-
73-
[text user mention](tg://user?id=123456789)
74-
75-
`inline fixed-width code`
76-
77-
```
78-
pre-formatted
79-
fixed-width
80-
code block
81-
```
82-
83-
> Quoted text
84-
85-
**Example**:
86-
87-
.. code-block:: python
88-
89-
from pyrogram import enums
90-
91-
await app.send_message(
92-
"me",
93-
(
94-
"**bold**, "
95-
"__italic__, "
96-
"--underline--, "
97-
"~~strike~~, "
98-
"||spoiler||, "
99-
"[URL](https://pyrogram.org), "
100-
"`code`, "
101-
"```"
102-
"for i in range(10):\n"
103-
" print(i)"
104-
"```"
105-
),
106-
parse_mode=enums.ParseMode.MARKDOWN
107-
)
108-
10947
HTML Style
11048
----------
11149

@@ -184,6 +122,68 @@ To strictly use this mode, pass :obj:`~pyrogram.enums.HTML` to the *parse_mode*
184122
185123
&lt;my text&gt;
186124
125+
Markdown Style
126+
--------------
127+
128+
.. warning::
129+
130+
The Markdown style is not recommended for complex text formatting.
131+
If you want to use complex text formatting such as nested entities, overlapping entities use the HTML style instead.
132+
133+
134+
To strictly use this mode, pass :obj:`~pyrogram.enums.ParseMode.MARKDOWN` to the *parse_mode* parameter when using
135+
:meth:`~pyrogram.Client.send_message`. Use the following syntax in your message:
136+
137+
.. code-block:: text
138+
139+
**bold**
140+
141+
__italic__
142+
143+
--underline--
144+
145+
~~strike~~
146+
147+
||spoiler||
148+
149+
[text URL](https://pyrogram.org/)
150+
151+
[text user mention](tg://user?id=123456789)
152+
153+
`inline fixed-width code`
154+
155+
```
156+
pre-formatted
157+
fixed-width
158+
code block
159+
```
160+
161+
> Quoted text
162+
163+
**Example**:
164+
165+
.. code-block:: python
166+
167+
from pyrogram import enums
168+
169+
await app.send_message(
170+
"me",
171+
(
172+
"**bold**, "
173+
"__italic__, "
174+
"--underline--, "
175+
"~~strike~~, "
176+
"||spoiler||, "
177+
"[URL](https://pyrogram.org), "
178+
"`code`, "
179+
"```"
180+
"for i in range(10):\n"
181+
" print(i)"
182+
"```"
183+
),
184+
parse_mode=enums.ParseMode.MARKDOWN
185+
)
186+
187187
Different Styles
188188
----------------
189189

@@ -236,18 +236,18 @@ strike` styles, and you can still combine both Markdown and HTML together.
236236

237237
Here there are some example texts you can try sending:
238238

239-
**Markdown (Not Recommended)**:
240-
241-
- ``**bold, --underline--**``
242-
- ``**bold __italic --underline ~~strike~~--__**``
243-
- ``**bold __and** italic__``
244-
245239
**HTML**:
246240

247241
- ``<b>bold, <u>underline</u></b>``
248242
- ``<b>bold <i>italic <u>underline <s>strike</s></u></i></b>``
249243
- ``<b>bold <i>and</b> italic</i>``
250244

245+
**Markdown (Not Recommended)**:
246+
247+
- ``**bold, --underline--**``
248+
- ``**bold __italic --underline ~~strike~~--__**``
249+
- ``**bold __and** italic__``
250+
251251
**Combined**:
252252

253253
- ``--you can combine <i>HTML</i> with **Markdown**--``

0 commit comments

Comments
 (0)