[FFmpeg-devel] [PATCH] web/index: fix invalid line-break (BR) tags

[FFmpeg-devel] [PATCH] web/index: fix invalid line-break (BR) tags

[Marth64]

Signed-off-by: Marth64 <marth64@proxyid.net>
---
 src/index | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/src/index b/src/index
index 98cc516..a949270 100644
--- a/src/index
+++ b/src/index
@@ -113,11 +113,11 @@
   </p>
   <p>
     Internally, we have had a number of changes too. The FFT, MDCT, DCT and DST implementation used for codecs
-    and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).</br>
-    This also led to a reduction in the the size of the compiled binary, which can be noticeable in small builds.</br>
+    and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).<br />
+    This also led to a reduction in the the size of the compiled binary, which can be noticeable in small builds.<br />
     There was a very large reduction in the total amount of allocations being done on each frame throughout video decoders,
-    reducing overhead.</br>
-    RISC-V optimizations for many parts of our DSP code have been merged, with mainly the large decoders being left.</br>
+    reducing overhead.<br />
+    RISC-V optimizations for many parts of our DSP code have been merged, with mainly the large decoders being left.<br />
     There was an effort to improve the correctness of timestamps and frame durations of each packet, increasing the
     accurracy of variable frame rate video.
   </p>
@@ -1471,15 +1471,15 @@
     Following our previous post regarding our participation on this year's
     OPW (Outreach Program for Women), we are now reaching out to our users
     (both individuals and companies) to help us gather the needed money to
-    secure our spot in the program.<br>
+    secure our spot in the program.<br />
     We need to put together 6K USD as a minimum but securing more funds would
-    help us towards getting more than one intern.<br>
+    help us towards getting more than one intern.<br />
     You can donate by credit card using
     <a href="https://co.clickandpledge.com/advanced/default.aspx?wid=56226">
     Click&amp;Pledge</a> and selecting the "OPW" option. If you would like to
     donate by money transfer or by check, please get in touch by
     <a href="mailto:opw@ffmpeg.org">e-mail</a> and we will get back to you
-    with instructions.<br>Thanks!
+    with instructions.<br />Thanks!
   </p>
 
   <h3 id="newweb">July 20, 2014, New website</h3>
-- 
2.34.1

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] [PATCH] web/index: fix invalid line-break (BR) tags

[Stefano Sabatini]

On date Monday 2024-01-08 15:13:18 -0600, Marth64 wrote:
> Signed-off-by: Marth64 <marth64@proxyid.net>
> ---
>  src/index | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/src/index b/src/index
> index 98cc516..a949270 100644
> --- a/src/index
> +++ b/src/index
> @@ -113,11 +113,11 @@
>    </p>
>    <p>
>      Internally, we have had a number of changes too. The FFT, MDCT, DCT and DST implementation used for codecs
> -    and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).</br>
> -    This also led to a reduction in the the size of the compiled binary, which can be noticeable in small builds.</br>

> +    and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).<br />

Check this:
https://stackoverflow.com/questions/1946426/html-5-is-it-br-br-or-br

From the HTML specs:
|[Void elements] are forbidden from containing any content at all. In
|HTML, these elements have a start tag only. The self-closing tag
|syntax may be used. The end tag must be omitted because the element is
|automatically closed by the parser.

Therefore the most correct form should be <br>.

In practice, I think this should make no difference since browsers
deal with that.

For consistency, it might be good to convert everything to <br>
though.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-devel] [PATCH] web/index: fix invalid line-break (BR) tags

[Marth64]

I am good with that, will update. I am used to XHTML so did that style.
Either way I just wanted to fix the truly invalid ones (</br>). Thank you!

On Tue, Jan 9, 2024 at 5:30 PM Stefano Sabatini <stefasab@gmail.com> wrote:

> On date Monday 2024-01-08 15:13:18 -0600, Marth64 wrote:
> > Signed-off-by: Marth64 <marth64@proxyid.net>
> > ---
> >  src/index | 14 +++++++-------
> >  1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/src/index b/src/index
> > index 98cc516..a949270 100644
> > --- a/src/index
> > +++ b/src/index
> > @@ -113,11 +113,11 @@
> >    </p>
> >    <p>
> >      Internally, we have had a number of changes too. The FFT, MDCT, DCT
> and DST implementation used for codecs
> > -    and filters has been fully replaced with the faster libavutil/tx
> (full article about it coming soon).</br>
> > -    This also led to a reduction in the the size of the compiled
> binary, which can be noticeable in small builds.</br>
>
> > +    and filters has been fully replaced with the faster libavutil/tx
> (full article about it coming soon).<br />
>
> Check this:
> https://stackoverflow.com/questions/1946426/html-5-is-it-br-br-or-br
>
> From the HTML specs:
> |[Void elements] are forbidden from containing any content at all. In
> |HTML, these elements have a start tag only. The self-closing tag
> |syntax may be used. The end tag must be omitted because the element is
> |automatically closed by the parser.
>
> Therefore the most correct form should be <br>.
>
> In practice, I think this should make no difference since browsers
> deal with that.
>
> For consistency, it might be good to convert everything to <br>
> though.
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

[FFmpeg-devel] [PATCH v2] web/index: fix invalid line breaks (BR)

[Marth64]

Uses preferred convention for ffmpeg

Signed-off-by: Marth64 <marth64@proxyid.net>
---
 src/index | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/index b/src/index
index 98cc516..edf8100 100644
--- a/src/index
+++ b/src/index
@@ -113,11 +113,11 @@
   </p>
   <p>
     Internally, we have had a number of changes too. The FFT, MDCT, DCT and DST implementation used for codecs
-    and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).</br>
-    This also led to a reduction in the the size of the compiled binary, which can be noticeable in small builds.</br>
+    and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).<br>
+    This also led to a reduction in the the size of the compiled binary, which can be noticeable in small builds.<br>
     There was a very large reduction in the total amount of allocations being done on each frame throughout video decoders,
-    reducing overhead.</br>
-    RISC-V optimizations for many parts of our DSP code have been merged, with mainly the large decoders being left.</br>
+    reducing overhead.<br>
+    RISC-V optimizations for many parts of our DSP code have been merged, with mainly the large decoders being left.<br>
     There was an effort to improve the correctness of timestamps and frame durations of each packet, increasing the
     accurracy of variable frame rate video.
   </p>
-- 
2.34.1

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".