|
269 | 269 | # preceding the first character with a backslash (see <i>Escaping |
270 | 270 | # Text Markup</i>, below). |
271 | 271 | # |
272 | | -# === Hyperlinks |
| 272 | +# === Links |
273 | 273 | # |
274 | | -# Hyperlinks to the web starting with +http:+, +mailto:+, +ftp:+ or +www.+ |
| 274 | +# Links to starting with +http:+, +https:+, +mailto:+, +ftp:+ or +www.+ |
275 | 275 | # are recognized. An HTTP url that references an external image file is |
276 | | -# converted into an inline <img...>. Hyperlinks starting with +link:+ are |
277 | | -# assumed to refer to local files whose path is relative to the <tt>--op</tt> |
278 | | -# directory. |
| 276 | +# converted into an inline image element. |
279 | 277 | # |
280 | | -# Hyperlinks can also be of the form _label_[_url_], in which |
281 | | -# case _label_ is used in the displayed text, and _url_ is |
282 | | -# used as the target. If _label_ contains multiple words, |
283 | | -# put it in braces: {<em>multi word label</em>}[url]. |
| 278 | +# Links starting with <tt>rdoc-ref:</tt> will link to the referenced class, |
| 279 | +# module, method, file, etc. |
284 | 280 | # |
285 | | -# Example hyperlinks: |
| 281 | +# Links starting with +link:+ refer to local files whose path is relative to |
| 282 | +# the <tt>--op</tt> directory. |
286 | 283 | # |
287 | | -# link:RDoc.html |
288 | | -# http://rdoc.rubyforge.org |
| 284 | +# Links can also be of the form <tt>label[url]</tt>, in which case +label+ is |
| 285 | +# used in the displayed text, and +url+ is used as the target. If +label+ |
| 286 | +# contains multiple words, put it in braces: <tt>{multi word label}[url]<tt>. |
| 287 | +# |
| 288 | +# Example links: |
| 289 | +# |
| 290 | +# https://github.com/rdoc/rdoc |
289 | 291 | |
290 | 292 | # {RDoc Documentation}[http://rdoc.rubyforge.org] |
291 | | -# {RDoc Markup}[link:RDoc/Markup.html] |
| 293 | +# {RDoc Markup}[rdoc-ref:RDoc::Markup] |
292 | 294 | # |
293 | 295 | # === Escaping Text Markup |
294 | 296 | # |
295 | 297 | # Text markup can be escaped with a backslash, as in \<tt>, which was obtained |
296 | | -# with "<tt>\\<tt></tt>". Except in verbatim sections and between \<tt> tags, |
297 | | -# to produce a backslash, you have to double it unless it is followed by a |
| 298 | +# with <tt>\\<tt></tt>. Except in verbatim sections and between \<tt> tags, |
| 299 | +# to produce a backslash you have to double it unless it is followed by a |
298 | 300 | # space, tab or newline. Otherwise, the HTML formatter will discard it, as it |
299 | | -# is used to escape potential hyperlinks: |
| 301 | +# is used to escape potential links: |
300 | 302 | # |
301 | 303 | # * The \ must be doubled if not followed by white space: \\. |
302 | 304 | # * But not in \<tt> tags: in a Regexp, <tt>\S</tt> matches non-space. |
303 | 305 | # * This is a link to {ruby-lang}[www.ruby-lang.org]. |
304 | 306 | # * This is not a link, however: \{ruby-lang.org}[www.ruby-lang.org]. |
305 | | -# * This will not be hyperlinked to \RDoc::RDoc#document |
| 307 | +# * This will not be linked to \RDoc::RDoc#document |
306 | 308 | # |
307 | 309 | # generates: |
308 | 310 | # |
309 | 311 | # * The \ must be doubled if not followed by white space: \\. |
310 | 312 | # * But not in \<tt> tags: in a Regexp, <tt>\S</tt> matches non-space. |
311 | 313 | # * This is a link to {ruby-lang}[www.ruby-lang.org] |
312 | 314 | # * This is not a link, however: \{ruby-lang.org}[www.ruby-lang.org] |
313 | | -# * This will not be hyperlinked to \RDoc::RDoc#document |
| 315 | +# * This will not be linked to \RDoc::RDoc#document |
314 | 316 | # |
315 | | -# Inside \<tt> tags, more precisely, leading backslashes are removed |
316 | | -# only if followed by a markup character (<tt><*_+</tt>), a backslash, |
317 | | -# or a known hyperlink reference (a known class or method). So in the |
318 | | -# example above, the backslash of <tt>\S</tt> would be removed |
319 | | -# if there was a class or module named +S+ in the current context. |
| 317 | +# Inside \<tt> tags, more precisely, leading backslashes are removed only if |
| 318 | +# followed by a markup character (<tt><*_+</tt>), a backslash, or a known link |
| 319 | +# reference (a known class or method). So in the example above, the backslash |
| 320 | +# of <tt>\S</tt> would be removed if there was a class or module named +S+ in |
| 321 | +# the current context. |
320 | 322 | # |
321 | | -# This behavior is inherited from RDoc version 1, and has been kept |
322 | | -# for compatibility with existing RDoc documentation. |
| 323 | +# This behavior is inherited from RDoc version 1, and has been kept for |
| 324 | +# compatibility with existing RDoc documentation. |
323 | 325 | # |
324 | 326 | # === Conversion of characters |
325 | 327 | # |
|
378 | 380 | # # ... |
379 | 381 | # end |
380 | 382 | # |
381 | | -# Names of classes, files, and any method names containing an |
382 | | -# underscore or preceded by a hash character are automatically hyperlinked |
383 | | -# from comment text to their description. This hyperlinking works inside |
384 | | -# the current class or module, and with ancestor methods (in included modules |
385 | | -# or in the superclass). |
| 383 | +# Names of classes, files, and any method names containing an underscore or |
| 384 | +# preceded by a hash character are automatically linked from comment text to |
| 385 | +# their description. This linking works inside the current class or module, |
| 386 | +# and with ancestor methods (in included modules or in the superclass). |
386 | 387 | # |
387 | 388 | # Method parameter lists are extracted and displayed with the method |
388 | 389 | # description. If a method calls +yield+, then the parameters passed to yield |
|
0 commit comments