Extend CIP-0001 to cover internationalized content

[KtorZ]

(new addition = Translations section)

[rphair]

nicely done; answers all of my questions last phrased in #539 (comment) except the one that came up in the last hour's CIP meeting; ready to approve otherwise.

[rphair]

@KtorZ as per #539 (comment) we're going to get people leaving the CIP field out unless it's specified explicitly.

If not considered important to the human reader, and even if not used (as I would think it would be) to accumulate translations along with the originals by site building scripts, this number is ultimately like a primary key in a table that, failing everything else, will line up the CIP with its translation (even if URLs go out of date for instance).

[Ryun1]

I do wonder if for the Revision field we include a URL with the commit hash? something like 18e692b <https://github.com/cardano-foundation/CIPs/pull/539/commits/18e692b5525bb7909c3637e793a449e0c01bd47b>? This would make navigation easier, no need to manually search for the commit hash.

[rphair]

@Ryun1 how we considered this idea in the rapid-fire discussion at the meeting (and some in the GitHub threads w/@KtorZ afterward) was:

1. The original proposal URL needs to be there in full so that naive users can click into it without having to follow or deduce it from the dressing on the GitHub page for the translated document... since this takes some familiarity with GitHub to know how to do.
2. The commit hash does not require this convenience because anyone interested in a commit hash is a sophisticated user who will know where to find the History link on the web page for the canonical GitHub link in the translation header.

[Ryun1]

@rphair

I got lost in some of the rapid fire meeting discussions! 🤓

What you described does sound very reasonable to me and I am happy to approve.

For the sake of it, I guess the other downside of the current approach is that the only way the naive users can tell if their translation is behind the current CIP is by searching and following the commit trail. But this should not really be much of an issue, since merged CIPs do not change too much, thus translations are not too likely to be out of date quickly or frequenctly.