On Fri, 15 Apr 2022, Fernando Oleo Blanco wrote: > thank you for your comments. As you have picked up, HTML is not my > strongest language. > > I did not know that "<" and ">" had to scaped in HTML, I will try to > remember that.
No worries, Fernando. "<" and ">" require special handling in HTML since the otherwise mark tags such as <html>, <p>, <code> and the like. > Regarding the nested <ul>. Since I did not know HTML, I looked at how > nested structure/lists are generated. Since the changelog uses > sequences of <li> and <ul> to indent/create a nested list, so I did. I > wanted to have a "title" (Pattern matching) and then have the > explanation with the code. Therefore, I copied the <li>, <ul> sequence > to get another level of nesting. Ah, I see. I believe I've got it and committed the little adjustment below. > I checked my results by opening the file in Firefox (latest version) > and it renders properly as I would expect/as I just explained. Is this > not correct? Is Firefox trying to make it work/trying to understand > what I meant and reproducing it as such? Yes, browsers are relatively resilient and intelligently render things that technically may not be perfectly standards compliant - Postel's law and such. :) To validate a document, especially after bigger changes, the W3 validator ( https://validator.w3.org ) has proven very helpful. It allows you to easily upload a draft version and get immediate feedback. In any case, having documentation is more in important than detailed markup aspects, with which I and others can help - thank you for that! Gerald commit 771ba5f8386afe082d41f47d504b405784785ac7 Author: Gerald Pfeifer <ger...@pfeifer.com> Date: Sat Apr 16 07:12:53 2022 -0600 gcc-12: Fix two markup issues diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 9daf3c51..4f904bfd 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -221,14 +221,14 @@ a work-in-progress.</p> <code>exit when</code>. The following expression is therefore now valid <code>raise Constraint_Error with "Element is null" when Element = null;</code></li> - <li>Pattern matching</li> + <li>Pattern matching <ul> <li>The <code>case</code> statement has been extended to cover records and arrays as well as finer grained casing on scalar types. In the future it is expected to provide more compile time guarantees when accessing discriminated fields. Case exhaustion is supported for pattern matching. An example would - be <code><pre> + be <pre> type Sign is (Neg, Zero, Pos); function Multiply (S1, S2 : Sign) return Sign is @@ -236,7 +236,7 @@ function Multiply (S1, S2 : Sign) return Sign is when (Neg, Neg) | (Pos, Pos) => Pos, when (Zero, <>) | (<>, Zero) => Zero, when (Neg, Pos) | (Pos, Neg) => Neg); - </pre></code></li> + </pre></li> </ul> </li> </ul>
