From b1d0119bb823d1d878b62194534a9366f2b20b45 Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sat, 20 Apr 2024 18:13:03 +0200 Subject: [PATCH 01/13] reforamt examples --- Specification.pod6 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 5e121a32..94c151a7 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -2533,16 +2533,16 @@ C and C A standard web URL. For example: =begin code :allow - This module needs the LAME library - (available from L>) + This module needs the LAME library + (available from L>) =end code If the link does not start with C it is treated as being relative to the location of the current document: =begin code :allow - See also: L> and - L> + See also: L> and + L> =end code =end defn @@ -2553,8 +2553,8 @@ C A filename on the local system. For example: =begin code :allow - Next, edit the global config file (that is, either - L> or L>). + Next, edit the global config file (that is, either + L> or L>). =end code Filenames that don't begin with a C or a C<~> are relative From 20359d39d60ad0c4d2784abba289515c8ce1104e Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sat, 20 Apr 2024 18:16:51 +0200 Subject: [PATCH 02/13] reformat examples; tidy --- Specification.pod6 | 89 +++++++++++++++++++++++++++------------------- 1 file changed, 52 insertions(+), 37 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 94c151a7..fb0ff8c8 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -38,7 +38,7 @@ our L. =head3 New: =item embedding binary data into documents, C<=data>, C<:filename>, C<:encoding>, =item C<:mime-type> attribute for C<=include> and C<=data> blocks, - =item introduce С schema for use in =picture and C<=table>, + =item introduce C schema for use in =picture and C<=table>, =item render tables from CSV files, C<=table>, =item new markdown mode for parser, =item C> - extends inline markup features. @@ -807,6 +807,7 @@ is used, any whitespace at the start of each line is removed during rendering. In addition, within a delimited C<=begin para>/C<=end para> block, any blank lines are preserved. + =head3 Code blocks Code blocks are used to specify pre-formatted text (typically source @@ -1419,6 +1420,7 @@ The preceding example could equally have been specified: B<=end nested> =end code + =head3 Tables Simple tables can be specified in Podlite using a C<=table> block. @@ -1731,17 +1733,18 @@ Comments are useful for meta-documentation (documenting the documentation): and for temporarily removing parts of a document: =begin code :allow - =item # Retreat to remote Himalayan monastery + =item # Retreat to remote Himalayan monastery - =item # Learn the hidden mysteries of space and time + =item # Learn the hidden mysteries of space and time - =item # Achieve enlightenment + =item # Achieve enlightenment - B<=begin comment> - =item # Prophet! - B<=end comment> + B<=begin comment> + =item # Prophet! + B<=end comment> =end code + =head3 Data blocks The C<=data> block is used to embed various types of data directly into a document. @@ -1862,6 +1865,7 @@ I the point in the source where their contents will be used. C<=data> blocks are never rendered by the standard Podlite renderers. + =head3 Semantic blocks All uppercase block typenames are reserved for specifying standard @@ -1962,6 +1966,7 @@ B<3.EI> =end code =end nested + =head3 Table of contents The C<=toc> block is used to make an autogenerated table of contents (TOC) @@ -2037,6 +2042,7 @@ To enable the autogenerated TOC, controlled and maintained by render, set the C< document attribute for C<=pod> block. In this case, the specific configuration and outcome of the TOC are influenced by the settings of the concrete render implementation. + =head3 Include block The C<=include> block is a powerful tool that allows to reuse specific @@ -2100,6 +2106,7 @@ sources could potentially create vulnerabilities such as injecting harmful code or malicious material. Tools responsible for displaying and handling the content should be able to provide a warning in such situations. + =head3 Inserting pictures Podlite allows to include images using a C<=picture> block with an inline version @@ -2159,6 +2166,7 @@ Alternatively, you can define the image caption using the C<:caption> attribute. diag01.png =end code + =head3 Mathematical formulas To include mathematical formulas, use a C<=formula> block with an inline version @@ -2186,6 +2194,7 @@ It possible to define the formule caption using the C<:caption> attribute. x = \frac{-b \pm \sqrt{b^2 - 4ac}}{2a} =end code + =head3 Markdown support Podlite includes built-in support for Markdown, making it easy to include Markdown @@ -2230,7 +2239,7 @@ the flexibility of Markdown. =head2 Markup codes -Markup codes enable inline markup within the text of (most) Pod block types. +Markup codes enable inline markup within the text of (most) Podlite block types. They are a form of block that can contain only other markup codes. Specifically, markup codes can nest: @@ -2307,6 +2316,7 @@ B or focus of the surrounding text; that it is of I. Such content would typically be rendered in a bold style or in C< ... > tags. + =head3 Mistake marking It possible strikethrough words using the code C>, where 'O' stands @@ -2426,7 +2436,7 @@ used to indicate a component of a syntax or specification that should eventually be replaced by an actual value. For example: =begin code :allow - The basic C command is: C B R> + The basic C command is: C B R> =end code or: @@ -2501,13 +2511,14 @@ Moreover, the C> code automatically treats its contents as being verbatim, which often eliminates the need for the C> as well: =begin code :allow - In Perl 5 POD, the B«V>>» code was widely used to break up text - that would otherwise be considered mark-up. + In certain scenarios, the B«V>>» code was widely used to break up text + that would otherwise be considered mark-up. =end code The C> markup code is the inline equivalent of a L block|#Comments>. + =head3 Links The C> code is used to specify all kinds of links, filenames, citations, @@ -2574,7 +2585,7 @@ An email address. Typically, activating this type of link invokes a mailer. For example: =begin code :allow - Please forward bug reports to L> + Please forward bug reports to L> =end code =end defn @@ -2585,8 +2596,8 @@ C A link to the system manpages. For example: =begin code :allow - This module implements the standard - Unix L> facilities. + This module implements the standard + Unix L> facilities. =end code =end defn @@ -2653,12 +2664,12 @@ A link to the L or L definition of the specified term within the current document. For example: =begin code :allow - He was highly prone to B>: an unfortunate proclivity - for employing grandiloquisms (for example, words such as "proclivity", - "grandiloquism", and indeed "lexiphania"). + He was highly prone to B>: an unfortunate proclivity + for employing grandiloquisms (for example, words such as "proclivity", + "grandiloquism", and indeed "lexiphania"). - B<=defn glossoligation> - Restraint of the tongue (voluntary or otherwise) + B<=defn glossoligation> + Restraint of the tongue (voluntary or otherwise) =end code and later, to link back to the definition @@ -2678,8 +2689,8 @@ The International Standard Book Number or International Standard Serial Number for a publication. For example: =begin code :allow - The Perl Journal was a registered - serial publication (L>) + The Perl Journal was a registered + serial publication (L>) =end code =end defn @@ -2730,14 +2741,15 @@ vertical bar. Whitespace is not significant on either side of the bar. For example: =begin code :allow - This module needs the Lhttp://www.mp3dev.org/mp3/>. + This module needs the Lhttp://www.mp3dev.org/mp3/>. - You could also write the code - L doc:Lingua::Romana::Perligata> + You could also write the code + L doc:Lingua::Romana::Perligata> - His Ldefn:lexiphania>> tendencies were, alas, incurable. + His Ldefn:lexiphania>> tendencies were, alas, incurable. =end code + =head3 Contextual backlinks Podlite introduces the concept of contextual backward links C> (or contextual backlinks), @@ -2750,13 +2762,13 @@ of the referenced material. For example: =begin code :allow - This text can reveal the meaning of B> + This text can reveal the meaning of B> =end code or: =begin code :allow - We discuss here about B>. + We discuss here about B>. =end code Contextual backlinks on the destination page can be displayed in various ways. @@ -2771,6 +2783,7 @@ all available link schemes, including C and C, to link to external Contextual backlinks might be visually distinguished from standard links through color coding. + =head3 Alias placements The C> code is replaced by the contents of the named alias or object @@ -2778,15 +2791,14 @@ specified within its delimiters. For example: =begin code - =alias PROGNAME Earl Irradiatem Eventually - =alias VENDOR 4D Kingdoms - =alias TERMS_URL L + =alias PROGNAME Earl Irradiatem Eventually + =alias VENDOR 4D Kingdoms + =alias TERMS_URL L - The use of A is subject to the terms and conditions - laid out by A, as specified at A. + The use of A is subject to the terms and conditions + laid out by A, as specified at A. =end code - See L<#Aliases> for further details of the aliasing macro mechanism. @@ -3006,10 +3018,11 @@ pre-configured option. For example, given the code blocks configurations in the previous example, to specify another language for code block: =begin code - =for code :lang - print(JSON.stringify([1,2]])); + =for code :lang + print(JSON.stringify([1,2]])); =end code + =head3 Pre-configuring markup codes You can also lexically preconfigure a L, @@ -3026,6 +3039,7 @@ Note that, even though the markup code is named using single-angles, the preconfiguration applies regardless of the actual delimiters used on subsequent instances of the code. + =head2 Aliases The C<=alias> directive provides a way to define lexically scoped @@ -3096,6 +3110,7 @@ text ever has to be changed, it need only be modified in a single place: =alias TERMS_URLS L =end code + =head2 Notification blocks These blocks, often referred to as admonitions, callouts, or alerts, @@ -3103,7 +3118,7 @@ serve to draw the reader's attention to different types of content, such as tips, warnings, or important notes. To create specially formatted blocks to highlight information in Podlite -the =nested block and :notice attribute are utilized. +the C<=nested> block and C<:notice> attribute are utilized. For example: @@ -3238,7 +3253,7 @@ icons that indicate the significance of the content. C> Space characters to be preserved C> Terminal output (typically rendered fixed-width) C> Unusual (typically rendered with underlining) - C<...>> Verbatim (internal markup codes ignored) + C«V<...>» Verbatim (internal markup codes ignored) C> Contextual backlinks C> reserved C> Index entry (C|R,R;...>>) From d63aa8a0eb333077c90585fcef161fff0d447219 Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 11:44:38 +0200 Subject: [PATCH 03/13] reformat examples; tidy --- Specification.pod6 | 49 +++++++++++++++++++++++----------------------- 1 file changed, 25 insertions(+), 24 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index fb0ff8c8..2e432963 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -628,6 +628,7 @@ in L. Podlite offers notations for specifying a wide range of standard block types... + =head3 Headings Podlite provides an unlimited number of levels of heading, specified by the @@ -1706,7 +1707,7 @@ plug-ins. For example: or: =begin code - =Image http://www.perlfoundation.org/images/perl_logo_32x104.png + =Image http://www.perlfoundation.org/images/perl_logo_32x104.png =end code Alongside the verbatim or placeholder content, the renderer could provide @@ -2700,21 +2701,21 @@ document, add the name of that section after the main link, separated by a C<#>. For example: =begin code :allow - Also see: L>, - L>, and - L> + Also see: L>, + L>, and + L> =end code To refer to a section of the current document, omit the external address: =begin code :allow - This mechanism is described under L> below. + This mechanism is described under L> below. =end code The scheme name may also be omitted in that case: =begin code :allow - This mechanism is described under L> below. + This mechanism is described under L> below. =end code Podlite include the possibility of assigning a unique identifier to a block. @@ -2723,12 +2724,12 @@ the C<:id> attribute. Later, these identifiers are utilized for adressing blocks and creating links. =begin code :allow - =for head1 :id - Introduction - =for para B<:id> - This is an introductory paragraph. - - For more information, see L> and L> + =for head1 :id + Introduction + =for para B<:id> + This is an introductory paragraph. + + For more information, see L> and L> =end code In this example, the link reference to the header block identified by "intro" @@ -2887,9 +2888,9 @@ You can specify an index entry in which the indexed text and the index entry are different, by separating the two with a vertical bar: =begin code :allow - An B> is an ordered list of scalars indexed by number, - starting with 0. A B> is an unordered collection of - scalar values indexed by their associated string key. + An B> is an ordered list of scalars indexed by number, + starting with 0. A B> is an unordered collection of + scalar values indexed by their associated string key. =end code In the two-part form, the index entry comes after the bar and is @@ -2899,26 +2900,26 @@ You can specify hierarchical index entries by separating indexing levels with commas: =begin code :allow - An X> is an ordered list of scalars - indexed by number, starting with 0. A X> - is an unordered collection of scalar values indexed by their - associated string key. + An X> is an ordered list of scalars + indexed by number, starting with 0. A X> + is an unordered collection of scalar values indexed by their + associated string key. =end code You can specify two or more entries for a single indexed text, by separating the entries with semicolons: =begin code :allow - A X> - is an unordered collection of scalar values indexed by their - associated string key. + A X> + is an unordered collection of scalar values indexed by their + associated string key. =end code The indexed text can be empty, creating a "zero-width" index entry: =begin code :allow - B>This is called the "Orcish Manoeuvre" - because you "OR" the "cache". + B>This is called the "Orcish Manoeuvre" + because you "OR" the "cache". =end code From 6146956213630b969d7d305e2f7361837a012124 Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 11:46:09 +0200 Subject: [PATCH 04/13] reformat examples; tidy --- Specification.pod6 | 35 +++++++++++++++++++---------------- 1 file changed, 19 insertions(+), 16 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 2e432963..19f385f8 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -167,6 +167,7 @@ Any other file extension puts the parser in default mode. The L block|#Include block > has a mechanism to override this behavior by using the C<:mime-type> attribute for the included files. + =head3 Delimited blocks Delimited blocks are bounded by C<=begin> and C<=end> markers, both of @@ -314,6 +315,7 @@ For example: Note that abbreviated blocks cannot specify configuration information. If configuration is required, use a C<=for> or C<=begin>/C<=end> instead. + =head3 Block equivalence The underlying documentation model treats all block @@ -326,24 +328,25 @@ three forms equally. For example, although L<#Headings> shows only: =begin code - =head1 Top Level Heading + =head1 Top Level Heading =end code this automatically implies that you could also write that block as: =begin code - =for head1 - Top Level Heading + =for head1 + Top Level Heading =end code or: =begin code - =begin head1 - Top Level Heading - =end head1 + =begin head1 + Top Level Heading + =end head1 =end code + =head3 Standard configuration options Podlite predefines a small number of standard configuration options that can be @@ -1827,7 +1830,7 @@ edited. =end defn =begin defn -C +C<:encoding> This option specifies the encoding method used to store the data. For non-text data, such as images in the PNG format, @@ -1838,15 +1841,15 @@ Example of storing images in C<=data> blocks: =begin code :allow - =begin data :key :filename :mime-type - = :access-time<2022-01-01T00:00:00Z> :modify-time<2022-01-02T10:00:00Z> - = :encoding - iVBORw0KGgoAAAANSUhEUgAAAAMAAAAFCAYAAACAcVaiAAAAS0lEQVR4AWPOPfjpvWZSW4db - ZLk+kwTHP24HUQYGfi4WTiZVAcYfDtIMDCJc/38xK6TWth37wcrw7cufF8yeeWUGrL8Z33Ey - /t0HAMBnF2nt5sNRAAAAAElFTkSuQmCC - =end data + =begin B B<:key> :filename :mime-type + = :access-time<2022-01-01T00:00:00Z> :modify-time<2022-01-02T10:00:00Z> + = :encoding + iVBORw0KGgoAAAANSUhEUgAAAAMAAAAFCAYAAACAcVaiAAAAS0lEQVR4AWPOPfjpvWZSW4db + ZLk+kwTHP24HUQYGfi4WTiZVAcYfDtIMDCJc/38xK6TWth37wcrw7cufF8yeeWUGrL8Z33Ey + /t0HAMBnF2nt5sNRAAAAAElFTkSuQmCC + =end data - =picture data:Logo + =picture B =end code @@ -2017,7 +2020,7 @@ The C<:folded-levels> attribute indicates which level of the TOC should be folded. =begin code :allow - =for toc :folded-levels[2,3] :caption('Table of contents') + =for toc B<:folded-levels[2,3]> :caption('Table of contents') head1, head2, item1 =end code From eb118f671140cab7ab41aba4366c46a3dbe8a6bb Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 13:53:19 +0200 Subject: [PATCH 05/13] update README --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index d11b8fe8..2c7d124f 100644 --- a/README.md +++ b/README.md @@ -19,6 +19,13 @@ Its flexibility makes it an ideal tool for creating documentation, blogs, educat Podlite aims to provide users with a means for creativity and expressing ideas in a structured form, while ensuring ease of use and high flexibility in content creation. +Supported file extensions: + +| Processor mode | Extensions +| ------------------| ----------- +| `Pod` mode | `.podlite`, `.pod6` (supported through history) +| | `*.*` - processes files under supported MIME types and/or extracts Podlite markup +| `Markdown` mode | `.md`, `.markdown` [The specification](https://github.com/podlite/podlite-specs/blob/main/Specification.pod6) for the Podlite markup language is written using Podlite markup itself. From 3efc8bc39e229cf79f98280c66bfcf9d74a81127 Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 13:53:52 +0200 Subject: [PATCH 06/13] Custom markup codes --- Specification.pod6 | 36 ++++++++++++++++++++---------------- 1 file changed, 20 insertions(+), 16 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 19f385f8..8e4fad6f 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -2954,38 +2954,42 @@ E Plants grow without soil, using mineral nutrient solutions. =end nested -=head3 Module-defined handler for extends markup features +=for head3 :id('Custom markup codes') +Module-defined handler for extends markup features The C> code in Podlite extends the language's capabilities by allowing users to specify additional processing instructions within their documents. -This is achieved by combining content text with a custom scheme specifier, -followed by extra content that is passed verbatim to a handler function. +This is achieved by combining content text with a custom plug-in specifier, +followed by optional configuration information that is passed to a handler function. The structure of the C> markup code as follows: - M< CONTENT-TEXT|SCHEME: VERBATIM_EXTRA_CONTENT> + M< CONTENT-TEXT| R R> -This syntax includes an optional CONTENT-TEXT section, followed by a - scheme specifier (SCHEME:) and then the VERBATIM_EXTRA_CONTENT. -The scheme specifier should follow the same rules as for L. -The scheme specifier allows the verbatim extra content (VERBATIM_EXTRA_CONTENT), -which may include additional attributes or instructions for the markup code handler. +This syntax includes C section, followed by a +name specifier C and then the C +(see L<"Configuration syntax options"|#configuration_syntax>). +The name specifier should follow the same rules as for +L. + +The C> formatting code is the inline equivalent of a +L. An example of how this code might be used is : =for code :allow - B This text is highlighted in yellowB<|Marker: yellow>>. + B«M<» This text is highlighted in yellow B«|Marker :color('yellow') >». In this example, the text C<"This text is highlighted in yellow"> is subject -to special handling specified by the C scheme and C, indicating -that the textshould be highlighted in yellow. +to special handling specified by the C module and +C<:color('yellow')>, indicating that the text should be highlighted in yellow. -If the C is unrecognized, the content text (CONTENT-TEXT) should be +If the C is unrecognized, the content text C should be rendered as ordinary text. This ensures that documents remain readable even -if specific processing instructions cannot be executed. +if specific processing instructions cannot be executed. The renderer could provide +an unobtrusive yet informative error message, explaining that the custom +markup block could not be processed. -This feature enhances the flexibility and capability of Podlite documents, -enabling custom markup and behavior that goes beyond standard markup features. =head2 Block pre-configuration From 862849ccf895909a03698dc24a9098e020b3c04e Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 13:54:32 +0200 Subject: [PATCH 07/13] format examples; tidy --- Specification.pod6 | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 8e4fad6f..2b2b5a49 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -1939,7 +1939,7 @@ The use of these special blocks is not required; you can still just write: =begin code =head1 SYNOPSIS - =begin code + =begin code :lang use Magic::Parser my Magic::Parser $parser .= new(); @@ -2069,7 +2069,7 @@ A wildcard L<"Selector"|#Selectors> serves this purpose, enabling inclusion of content from all the Markdown files: =begin code -=include file:./includes/*.md + =include file:./includes/*.md =end code It's possible to include blocks from the same document being worked on. @@ -2205,7 +2205,8 @@ Podlite includes built-in support for Markdown, making it easy to include Markdo content within Podlite documents. This is achieved using the C<=markdown> block. =begin code :allow - =begin markdown + B<=begin markdown> + ## Markdown Example You can use all the standard Markdown syntax within this block. For example: @@ -2234,7 +2235,7 @@ content within Podlite documents. This is achieved using the C<=markdown> block. > This is a blockquote. - =end markdown + B<=end markdown> =end code This block allows to seamlessly combine Podlite's structured blocks with From fa4534b12c4d78108bfd9aff7f445596e6f7cb96 Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 13:54:52 +0200 Subject: [PATCH 08/13] Named or modular custom blocks --- Specification.pod6 | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 2b2b5a49..5d232519 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -1695,9 +1695,10 @@ For example: =end code -=head3 Custom blocks +=for head3 :id +Named or modular custom blocks -Blocks whose names contain at least one uppercase and one lowercase +D whose names contain at least one uppercase and one lowercase letter are assumed to be destined for specialized renderers or parser plug-ins. For example: @@ -1713,13 +1714,31 @@ or: =Image http://www.perlfoundation.org/images/perl_logo_32x104.png =end code +=begin nested :notify +Named or modular blocks are defined within separate modules +and integrated into the core system through a defined interface or API. + +The interface or API for external modules depends on the implementation. +=end nested + +Ideally, each named block should have a corresponding handler responsible +for its rendering and processing. + +In the absence of a handler for named block, the implementation should +allow the content to degrade gracefully, ensuring that the core message +or functionality remains accessible even if some advanced features cannot +be rendered. As result, that blocks my be displayed as verbatim or +placeholder content or even not rendered at all. + Alongside the verbatim or placeholder content, the renderer could provide -an unobtrusive yet informative error message, explaining that the Custom block +an unobtrusive yet informative error message, explaining that the named block could not be processed. Note that all block names consisting entirely of lowercase or entirely of uppercase letters are reserved. See L<#Semantic blocks>. +To check custom markup codes, refer to L<#Custom markup codes>. + =head3 Podlite comments From 5b980685e958beaa98fb780cb8620a11af92425b Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 13:55:19 +0200 Subject: [PATCH 09/13] fix examples; add linking --- Specification.pod6 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 5d232519..c85cd443 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -181,7 +181,7 @@ configuration information for the block. This information is used in different ways by different types of blocks, but is always specified using any of: -=for table :nested +=for table :nested :caption("Configuration syntax options") :id Value is... Specify with... Or with... Or with... =============== =================== ============== ====================== Boolean (true) C«:key» C«:key(1)» C«key => 1» @@ -1982,7 +1982,7 @@ C<=SYNOPSIS> block of the preceding example might be rendered like so: =begin nested B<3.EI> -=begin code +=begin code :lang use Raku::Magic::Parser; my $rep = Raku::Magic::Parser.parse($fh, :all_pod); From bc2f558d5b99cbe91ccf470512ee40595b32842d Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 13:55:44 +0200 Subject: [PATCH 10/13] update changes --- Specification.pod6 | 26 +++++++------------------- 1 file changed, 7 insertions(+), 19 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index c85cd443..a681b79a 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -22,33 +22,21 @@ our L. =item Aliaksandr Zahatski |mailto:zag@cpan.org>> =end AUTHORS -=VERSION 1.0-beta3 +=VERSION 1.0 =begin CHANGES - -=head2 1.0-beta3 -=head3 New: - =item Notification blocks, C<:notify> attribute for C<=nested> blocks, - =item C<:folded> attribute, - =item C<:folded-levels> for C<=toc> block, - =item Refactor custom blocks and markup codes, C>. -=head3 Deprecated/removed: - =item Contextual aliases -=head2 1.0-beta2 +=head2 1.0 =head3 New: + =item Notification blocks, C<:notify> attribute for C<=nested> blocks, + =item C<:folded> attribute, + =item C<:folded-levels> for C<=toc> block, + =item Refactor Named custom blocks and markup custom codes, C>, =item embedding binary data into documents, C<=data>, C<:filename>, C<:encoding>, =item C<:mime-type> attribute for C<=include> and C<=data> blocks, =item introduce C schema for use in =picture and C<=table>, =item render tables from CSV files, C<=table>, =item new markdown mode for parser, - =item C> - extends inline markup features. - -=head3 Deprecated/removed: - =item C<=finish>, - =item markers in comments. - -=head2 1.0-beta1 -=head3 New: + =item C> - extends inline markup features, =item add C<:id>, C<:caption>, C<:lang> attributes, =item task lists, C<=item> and C<:checked> attribute, =item intro Selectors, From 3e1269cfcfae24b4003c5aa781939fec70dbba1b Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 13:55:54 +0200 Subject: [PATCH 11/13] update changes --- Specification.pod6 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index a681b79a..2b7f685f 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -51,8 +51,10 @@ our L. =item contextual backlinks, C>, =item advanced table format, C<=row>,C<=cell> blocks, C<:header>, C<:rowspan>, C<:colspan> attributes. - =head3 Deprecated/removed: + =item Contextual aliases, + =item C<=finish>, + =item markers in comments, =item C<:margin> attribute, =item C<=encoding> directive, =item C> due to C<=toc> block, @@ -61,7 +63,6 @@ our L. =item Declarator block, =item C<:formatted> attribute, =item C<:like> attribute. - =end CHANGES =head1 Podlite From bc79ff8dfdbc05b9992b1da87a21ae98b8186521 Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Sun, 21 Apr 2024 14:31:08 +0200 Subject: [PATCH 12/13] update examples --- Specification.pod6 | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/Specification.pod6 b/Specification.pod6 index 2b7f685f..6cf1a98e 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -5,14 +5,13 @@ This file is deliberately specified in Podlite format =TITLE Podlite - a lightweight markup language -=begin nested :notify :caption('This document is still being worked on!') - -It's not finished yet, but it's available for everyone to see -and comment on. This way, it can get better with everyone's input. +=begin nested :notify :caption('Work on the next release continues!') If you have any ideas to make it better, or if you have any questions, you're welcome to suggest changes or start a conversation on -our L. +our L. + +Looking forward to working on the next release with your valuable input. =end nested =toc head1, head2, head3 @@ -25,7 +24,7 @@ our L. =VERSION 1.0 =begin CHANGES -=head2 1.0 +=head2 v1.0 =head3 New: =item Notification blocks, C<:notify> attribute for C<=nested> blocks, =item C<:folded> attribute, @@ -1673,7 +1672,7 @@ For example: =for table :caption('Basic cake recipe ingredients') B - =begin data :key :mime-type + =begin data B<:key> :mime-type ingredient,quantity,unit flour,2,cups sugar,1,cups @@ -1778,19 +1777,19 @@ Each C<=data> block can be given a C<:key> option, to name it. The contents of any C<=data> block with a key are addressable via the C schema. For example: -=begin code - =begin data :key :mime-type +=begin code :allow + =begin data B<:key> :mime-type id,name,position,department 1,John Doe,Manager,Marketing 2,Jane Smith,Developer,Engineering 3,Bob Brown,Designer,Product =end data - =table data:employee_data + =table B =end code -Each =data block can include several attributes to provide additional information +Each C<=data> block can include several attributes to provide additional information about the contained data: =begin defn From e3cca3cb81bb989590fa767aea82beadabd272d0 Mon Sep 17 00:00:00 2001 From: Aliaksandr Zahatski Date: Tue, 23 Apr 2024 21:25:23 +0200 Subject: [PATCH 13/13] fix syntax --- Specification.pod6 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Specification.pod6 b/Specification.pod6 index 6cf1a98e..9d411262 100644 --- a/Specification.pod6 +++ b/Specification.pod6 @@ -32,7 +32,7 @@ Looking forward to working on the next release with your valuable input. =item Refactor Named custom blocks and markup custom codes, C>, =item embedding binary data into documents, C<=data>, C<:filename>, C<:encoding>, =item C<:mime-type> attribute for C<=include> and C<=data> blocks, - =item introduce C schema for use in =picture and C<=table>, + =item introduce C schema for use in C<=picture> and C<=table>, =item render tables from CSV files, C<=table>, =item new markdown mode for parser, =item C> - extends inline markup features,