93. From: Standards <standards-boun...@xmpp.org> on behalf of Sam Whited <s...@samwhited.com>Sent: 08 March 2018 16:35To: standards@xmpp.orgSubject: Re: [Standards] XEP-0393 and XEP-0394 naming On Thu, Mar 8, 2018, at 10:26, Kozlov Konstantin wrote:> Yes, maybe. It was just an example.In
From: Standards on behalf of Sam Whited
Sent: 08 March 2018 16:35
To: standards@xmpp.org
Subject: Re: [Standards] XEP-0393 and XEP-0394 naming
On Thu, Mar 8, 2018, at 10:26, Kozlov Konstantin wrote:
> Yes, maybe. It was just an example.
Indeed. I'm okay with renaming if others agree tha
Hello!8 марта 2018 г. 21:26 пользователь VanitasVitae написал:Also if we'd do that, we'd have "Message Markup" and "Message Markdown"...Yeah, but it will be really funny. Just like "more" and "less" viewers Linux! :-)With my best regardsKonstantin___
Sta
On Thu, Mar 8, 2018, at 10:26, Kozlov Konstantin wrote:
> Yes, maybe. It was just an example.
Indeed. I'm okay with renaming if others agree that "styling" is confusing for
some reason, but only if someone comes up with a name that expresses the intent
clearer.
"Message Markup", or "Lightweight
On Donnerstag, 8. März 2018 17:18:02 CET Kozlov Konstantin wrote:
> Hello!
>
> 08.03.2018, 19:03, "Sam Whited" :
> On Thu, Mar 8, 2018, at 10:01, Kozlov Konstantin wrote:
>
> I think "Markup" more suits
> for XEP-0393 and "Styling" for XEP-0394.I guess, we should think about
> renaming those
Also if we'd do that, we'd have "Message Markup" and "Message Markdown"...
Am 8. März 2018 17:23:32 MEZ schrieb Sam Whited :
>On Thu, Mar 8, 2018, at 10:18, Kozlov Konstantin wrote:
>> For example we may rename XEP-0393 to "Markdown" 'cause its syntax
>somewhat
>> similar to Markdown[1] language.
Hello! 08.03.2018, 19:24, "Sam Whited" :On Thu, Mar 8, 2018, at 10:18, Kozlov Konstantin wrote: For example we may rename XEP-0393 to "Markdown" 'cause its syntax somewhat similar to Markdown[1] language.That seems even more confusing than the other suggestion, because we'd be naming it "markdown"
Hello! 08.03.2018, 19:20, "Dave Cridland" :On 8 March 2018 at 16:18, Kozlov Konstantin wrote: The XEPs are not so widely implemented for the moment to care much about it.Actually, I think XEP-0393 has several implementations in widelydeployed clients.Yeah, sure. But I think, both
On Thu, Mar 8, 2018, at 10:18, Kozlov Konstantin wrote:
> For example we may rename XEP-0393 to "Markdown" 'cause its syntax somewhat
> similar to Markdown[1] language.
That seems even more confusing than the other suggestion, because we'd be
naming it "markdown" even though it's not markdown (o
On 8 March 2018 at 16:18, Kozlov Konstantin wrote:
> The XEPs are not so widely implemented for the moment to care much about it.
Actually, I think XEP-0393 has several implementations in widely
deployed clients.
I was considering suggesting a Last Call at this point.
Dave.
Hello! 08.03.2018, 19:03, "Sam Whited" :On Thu, Mar 8, 2018, at 10:01, Kozlov Konstantin wrote: I think "Markup" more suits for XEP-0393 and "Styling" for XEP-0394.I guess, we should think about renaming those XEPs to make their names less confusing.I'm not against this (as the author of 0393) if p
On Thu, Mar 8, 2018, at 10:01, Kozlov Konstantin wrote:
> I think "Markup" more suits
> for XEP-0393 and "Styling" for XEP-0394.I guess, we should think about
> renaming those XEPs to make their names
> less confusing.
I'm not against this (as the author of 0393) if people find this confusing, b
Hello! Discussing XEP-0393 and XEP-0394 I mixed them up a few times. That's because their names are really confusing. I think "Markup" more suits for XEP-0393 and "Styling" for XEP-0394.I guess, we should think about renaming those XEPs to make their names less confusing. With my best regards,Konst
13 matches
Mail list logo