all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Stephen J. Eglen" <stephen@eglen.org.uk>,
	Jack Kamm <jackkamm@gmail.com>,
	emacs-orgmode@gnu.org, mail@nicolasgoaziou.fr, steuer@hsu-hh.de
Subject: Re: Bug report for ox-icalendar: newlines should be CRLF
Date: Fri, 14 Apr 2023 12:45:39 +0200	[thread overview]
Message-ID: <ZDku03rBam5KAyTa@tuxteam.de> (raw)
In-Reply-To: <87wn2en543.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

On Fri, Apr 14, 2023 at 10:13:48AM +0000, Ihor Radchenko wrote:
> "Stephen J. Eglen" <stephen@eglen.org.uk> writes:
> 
> >> https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b51891996
> >
> > Thanks for copying me in on this.
> >
> > There is a related issue about EOLs, not just \r\n -- each line should
> > be a maximum of 75 characters; this is handled by 
> > org-icalendar-fold-string 
> 
> May you please provide a link to the iCalendar spec document section
> describing this requirement?

It's in rfc5545 [1], referenced to from rfc7986 [2].

Cheers
[1] https://datatracker.ietf.org/doc/html/rfc5545#section-3.1
[2] https://datatracker.ietf.org/doc/html/rfc7986#section-1
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-04-14 10:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06  8:30 Bug report for ox-icalendar: newlines should be CRLF Stephen J. Eglen
2023-01-08  8:50 ` Detlef Steuer
2023-02-01 14:51 ` Ihor Radchenko
2023-04-02 20:42   ` Jack Kamm
2023-04-03  8:09     ` Stephen J. Eglen
2023-04-14 10:13       ` Ihor Radchenko
2023-04-14 10:45         ` tomas [this message]
2023-04-14 16:38           ` Jack Kamm
2023-04-16  5:01             ` Jack Kamm
2024-01-12 13:54               ` Ihor Radchenko
2023-04-15  9:07           ` Stephen J. Eglen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZDku03rBam5KAyTa@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=jackkamm@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    --cc=stephen@eglen.org.uk \
    --cc=steuer@hsu-hh.de \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.