This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Sat Mar 30 13:24:56 CET 2013
On Sat, Mar 30, 2013 at 12:06 PM, Philipp Kern <philipp.kern at kit.edu> wrote: > ISO-8859-1 *and* UTF-8 content seems a tad ridiculous and backwards. I should have explained the rationale behind this suggestion, sorry. What it boils down to is that normal text would use the standard ASCII chars and only names and references would be allowed to use UTF-8. A different, and maybe better, way to put this is "UTF-8 for the document, but use only ASCII chars within the main text". Richard
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]