Riley, I've seen you some time ago I'm a 27 years old sexy chick longing for a sexy friend. I am ready to try anything in the bedroom ;)
are you interested? Please, lets meet today or tomorrow In case you want to see my dirty selfies, you can enjoy them: JessicaSmith pics <https://dately.baby?p=tljen&s=687474703a2f2f646174696e6773722e636f6d2f6e65772f3f733d393126263738363534373337383036343133342664693d37672d323435392665643d676d6126693d61646d696e39312c31323239322c7873616d6374796c6540676d61696c2e636f6d2c52696c65792674733d3137343732383239363626383637363332363137353638353938&?/Jess/photo193/> Kisses, Jessica On Tue, May 13, 2025, at 5:34 PM, Riley wrote: >??? What > чт, 15 мая 2025 г. в 02:49, <[email protected]>: > Send rfc-interest mailing list submissions to > [email protected] > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of rfc-interest digest..." > > Today's Topics: > > 1. RFC 9633 SVG is unreadable (was: Normative information in RFC > imagery) > (Martin Thomson) > 2. Re: RFC 9633 SVG is unreadable (was: Normative information in RFC > imagery) > (StJohns, Michael) > 3. Re: RFC 9633 SVG is unreadable (was: Normative information in RFC > imagery) > (Martin Thomson) > 4. Re: RFC 9633 SVG is unreadable (James Cloos) > 5. Re: RFC 9633 SVG is unreadable (Brian E Carpenter) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 15 May 2025 10:01:21 +1000 > From: "Martin Thomson" <[email protected]> > Subject: [rfc-i] RFC 9633 SVG is unreadable (was: Normative > information in RFC imagery) > To: "Jean Mahoney" <[email protected]> > Cc: rfc-interest <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain > > On Thu, May 15, 2025, at 00:16, Jean Mahoney wrote: > > (Artwork only available as SVG: see > > https://www.rfc-editor.org/rfc/rfc9633.html) > > > > Figure 1: Case A-1: Application Flow Aggregation > > Wow, I hadn't seen these diagrams before. They are completely > unreadable. The text is so small I needed a 240% zoom to make out some of > it. Appendix B.3 has a diagram that has text overlapping lines and missing > lines. At the same time, these are somewhat helpful, it's just that they > have far too much detail to be readable. > > I realize that these are just examples in appendices, but I don't think > that this are good examples. > > > ------------------------------ > > Message: 2 > Date: Wed, 14 May 2025 21:44:51 -0400 > From: "StJohns, Michael" <[email protected]> > Subject: [rfc-i] Re: RFC 9633 SVG is unreadable (was: Normative > information in RFC imagery) > To: Martin Thomson <[email protected]> > Cc: rfc-interest <[email protected]> > Message-ID: > <CANeU+ZA8MXQmDj7O9U3qt-SjcfewAMEB62LVzum= > [email protected]> > Content-Type: multipart/alternative; > boundary="00000000000075d11d063522d00b" > > Just took a look from an iPadMiniusing Safari. Perfectly readable. And > I’m myopic. But they are a bit dense. > > Mike > > On Wed, May 14, 2025 at 20:01 Martin Thomson <[email protected]> wrote: > > > On Thu, May 15, 2025, at 00:16, Jean Mahoney wrote: > > > (Artwork only available as SVG: see > > > https://www.rfc-editor.org/rfc/rfc9633.html) > > > > > > Figure 1: Case A-1: Application Flow Aggregation > > > > Wow, I hadn't seen these diagrams before. They are completely > > unreadable. The text is so small I needed a 240% zoom to make out some > of > > it. Appendix B.3 has a diagram that has text overlapping lines and > missing > > lines. At the same time, these are somewhat helpful, it's just that they > > have far too much detail to be readable. > > > > I realize that these are just examples in appendices, but I don't think > > that this are good examples. > > > > _______________________________________________ > > rfc-interest mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > > -------------- next part -------------- > A message part incompatible with plain text digests has been removed ... > Name: not available > Type: text/html > Size: 1738 bytes > Desc: not available > > ------------------------------ > > Message: 3 > Date: Thu, 15 May 2025 11:50:13 +1000 > From: "Martin Thomson" <[email protected]> > Subject: [rfc-i] Re: RFC 9633 SVG is unreadable (was: Normative > information in RFC imagery) > To: "Michael StJohns" <[email protected]> > Cc: rfc-interest <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=utf-8 > > On Thu, May 15, 2025, at 11:44, StJohns, Michael wrote: > > Just took a look from an iPadMiniusing Safari. Perfectly readable. > > And I’m myopic. But they are a bit dense. > > All screens are different. I have a very large screen and I'm unable to > read the text. If you want a format that is not too subjective or > dependent on screen size, check out Figure 17 in the PDF format. > > > ------------------------------ > > Message: 4 > Date: Wed, 14 May 2025 22:44:39 -0400 > From: James Cloos <[email protected]> > Subject: [rfc-i] Re: RFC 9633 SVG is unreadable > To: "Martin Thomson" <[email protected]> > Cc: rfc-interest <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain > > >>>>> "MT" == Martin Thomson <[email protected]> writes: > > MT> unreadable. The text is so small I needed a 240% zoom to make out > MT> some of it. Appendix B.3 has a diagram that has text overlapping > MT> lines and missing lines. > > that got me curious. > > here the svg is entirely unreadable. the text is taller than the boxes > and each letter also overlaps horizontally. > > having the screw around with html to read an rfc is already bogus. > > but that rfc is (typographically speaking) the worst example i've seen. > > at least the yang is readable in the proper text version. > > -JimC > -- > James Cloos <[email protected]> > OpenPGP: https://jhcloos.com/0x997A9F17ED7DAEA6.asc > > > ------------------------------ > > Message: 5 > Date: Thu, 15 May 2025 14:49:11 +1200 > From: Brian E Carpenter <[email protected]> > Subject: [rfc-i] Re: RFC 9633 SVG is unreadable > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 15-May-25 13:50, Martin Thomson wrote: > > On Thu, May 15, 2025, at 11:44, StJohns, Michael wrote: > >> Just took a look from an iPadMiniusing Safari. Perfectly readable. > >> And I’m myopic. But they are a bit dense. > > > > All screens are different. I have a very large screen and I'm unable to > read the text. If you want a format that is not too subjective or > dependent on screen size, check out Figure 17 in the PDF format. > > Up-levelling slightly, it seems reasonable to assert that blind people > would get precisely nothing out of this appendix. The text is fairly > pointless without the diagrams and json. Even the json examples are highly > visual - without the whitespace, they are very hard to parse - and I doubt > that most screen readers will read the json in a useful way. > > That doesn't mean the appendix is evil, but it does suggest to me that we > should focus accessibility requirements/suggestions on normative text. > > Brian > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > rfc-interest mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > ------------------------------ > > End of rfc-interest Digest, Vol 247, Issue 12 > ********************************************* >
_______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
