Re: [calsify] draft-ietf-calext-jscalendar - *this*, _this_ and "this"

[Doug Royer <[e-mail]>]

On 5/14/19 1:55 AM, Robert Stepanek [Masked] wrote:
> Preview: On Tue, May 14, 2019, at 3:32 AM, Doug Royer wrote: > On 5/13
> 
> Your Blur Masked Email [e-mail] received this from 
> [e-mail].
> Blur forwards Masked Emails to you here ? just reply like normal and 
> Blur keeps your email private.
> IF THIS IS SPAM, CLICK HERE TO BLOCK. 
> <https://dnt.abine.com/#/block_email/[e-mail]/[e-mail]>
> 
> Masked Emails stop spam, defy tracking, and keep data private. INVITE 
> FRIENDS TO TRY BLUR PREMIUM AT 50% OFF <https://dnt.abine.com/#/referral>.
> 
> On Tue, May 14, 2019, at 3:32 AM, Doug Royer wrote:
>> On 5/13/19 8:56 AM, Robert Stepanek [Masked] wrote:
>> >> 8. I am confused by highlighting meaning of *this*, _this_, and "this"
>> >> As described in 1.3 and the highlighting methods throughout this spec.
>> >> I have not seen these used in a draft before.
>> >
>> > The notation should make things simpler to read, not make them more
>> > confusing. I'm sorry if it failed on you. Would you have an example of
>> > an RFC which achieves this better? I'll also look at recent RFCs for
>> > different formats.
>>
>> Actually, I meant it literally. I am confused and do not understand
>> their meaning or difference at all.
> 
> Copying the relevant parts of section 1.3:
> 
> In this document, property and object definitions
> are formatted like *this* and are referred to in other sections like
> _this_. Verbatim text is formatted like "this".

*Because* _it_ "IS" confusing. No clue what it m_e_a_n_s.



-- 

Doug Royer - (http://DougRoyer.US)
[e-mail]
714-989-6135