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 <stefa...@gmail.com> wrote: > On date Monday 2024-01-08 15:13:18 -0600, Marth64 wrote: > > Signed-off-by: Marth64 <mart...@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-requ...@ffmpeg.org with subject "unsubscribe".
