Lines Matching refs:as

17 Parsing Markdown to HTML is as simple as calling a single method (see [Usage](#usage)) providing a …
20 Extending the Markdown language with new elements is as simple as adding a new method to the class …
23 of the Markdown text as an abstract syntax tree (see [Extending the language](#extend)).
81 …se your markdown you need only two lines of code. The first one is to choose the markdown flavor as
116 - `$parser->keepListStartNumber = true` to enable keeping the numbers of ordered lists as specified…
204 properties. For the different element types there are different ways to extend them as you will see…
208 The markdown is parsed line by line to identify each non-empty line as one of the block element typ…
209 To identify a line as the beginning of a block element it calls all protected class methods who's n…
223 		// if a line starts with at least 3 backticks it is identified as a fenced code block
241 …is the same name as used for the identify function above. The consume method also takes the lines …
294 Adding inline elements is different from block elements as they are parsed using markers in the tex…
321 …// return the parsed tag as an element of the abstract syntax tree and call `parseInline()` to all…
332 	// rendering is the same as for block elements, we turn the abstract syntax array into a string.
355 (`Markdown`, `GithubMarkdown` or `MarkdownExtra`) as your flavors base class.
371 		parseInlineHtml as private;
375 		identifyUl as protected identifyBUl;
376 		consumeUl as protected consumeBUl;
381 		identifyHr as protected identifyAHr;
382 		consumeHr as protected consumeAHr;
391 	 * Defaults to `false` which means that markup is formatted as HTML4.
409 and `identifyBUl` to `identifyBUl`. The consume function always has to have the same name as the id…
418 If you use the link trait it may be useful to implement `prepare()` as shown above to reset referen…
425 as is.
431 	 * as markdown.
474 as you have to come up with a complex regex, that matches your addition but does not mess
475 with other elements. Such additions are very common as you see on github which supports referencing
478 parse the tokens as they find them. The only implentation that I have found that uses
489 I chose this approach as it is easier to implement and also more intuitive approach compared
512 with it as long as you mention my name and include the [license file][license]. Check the [license]…