Re: keywords

Hi, with all the traffic lately, I wanted to put a few ideas together from
this thread before they got lost.

Alias-based solution to:
Keyword Internationalization & Short Keywords & Long Keywords & Custom
Aliases.

Summary:
For svn keyword translation, implement *just* the Long Keywords.
Provide an alias mechanism for defining custom keywords.

All the rest (internationalization, short keywords, id, etc) all become
just aliases.

So you would define short keywords, non-english keywords, custom aliases,
etc in a keyword_alias file/properties on a per-project basis.

More details:

There should be a basic default set of aliases, which includes the short
keywords, id, etc.
id: FileName Date Author Revision
Revision: LastChangedRevision
Date: LastChangedDate
Author: LastChangedBy

Then add what you need for your project:

(Whatever you need for the people working on your project to understand the
meaning of these fields. Please forgive the rough translations.)
Autor: Author
auteur: Author
Datums: Date
fecha: Date
Neuausgabe: Revision

Project specific:
FreeBSD: FileName FreeBSDVersion Date Author Revision
NetBSD: ... NetBSDVersion ...
(though never both defined in the same project...) It should ignore unknown
keywords.

This is far from all the details needed, but it's the basic format of a
keywords system that handles all the exception cases mentioned so far...
reduced to a single alias-based system.

Thoughts?

~Jonathan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:53 2006