From 7bd23628d21634c7d2e6c378465feb3ada37158a Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <tschwinge@gnu.org>
Date: Fri, 10 Mar 2006 21:18:00 +0000
Subject: none

---
 Distrib/DebianTranslatorPolicy.mdwn | 42 ++++++++++++++++++++++---------------
 1 file changed, 25 insertions(+), 17 deletions(-)

diff --git a/Distrib/DebianTranslatorPolicy.mdwn b/Distrib/DebianTranslatorPolicy.mdwn
index dff64549..7092a761 100644
--- a/Distrib/DebianTranslatorPolicy.mdwn
+++ b/Distrib/DebianTranslatorPolicy.mdwn
@@ -1,32 +1,40 @@
-This page describes the packaging policy for translators.
+**_This page describes the Debian packaging policy for translators._**
 
-## <a name="Naming_Scheme"> Naming Scheme </a>
+## <a name="Package_Naming_Scheme"> Package Naming Scheme </a>
 
-Possible package naming schemes (foo is a filesystem based translator, bar is a node based translator)
+Candidates for package naming schemes (_foofs_ is a filesystem based translator, e.g. _tarfs_, _bar_ is a node based translator, e.g. _random_):
 
-* foofs-translator, bar-translator [current favourite]
+* _foofs-translator_, _bar-translator_ [current favourite]
 
-* foofs, bar [this will make searching somewhat more of a hassle]
+* _foofs_, _bar_ [this will make searching somewhat more of a hassle and may easily conflict with already used package names]
 
-* foofs-trans, bar-trans
+* _foofs-trans_, _bar-trans_
 
-* hurd-translator-foofs, hurd-translator-bar
+* _hurd-translator-foofs_, _hurd-translator-bar_
 
-* source package should be called whatever the tarball/cvs module says
+Do we need to destinguish between file system and node based translators?
 
-* do we need to destinguish between file system and node based translators?
+Source packages should be called whatever the tarball/cvs module says.
 
-## <a name="Where_to_put_files"> Where to put files </a>
+## <a name="Where_to_Put_Files"> Where to Put Files </a>
 
-* They should go into /hurd
+The translators should go into _/hurd_.
 
-* What about setting passive translators in /servers or /dev?
+## <a name="What_about_setting_passive_trans"> What about setting passive translators in _/servers_ or _/dev_? </a>
 
-## <a name="Short_Long_description_guideline"> Short/Long description guidelines </a>
+The idea is that the package should set passive translators in its _postinst_ instructions.
 
-<dl>
-  <dt> [packagename]</dt>
-  <dd> Foo translator for [doing bar]<br /> Foo is a GNU/Hurd translator which does [bar] </dd>
-</dl>
+There may, however, be difficulties with that: it's perfectly valid to have two different _random_ translator packages installed (they won't conflict with each other as long as their file names don't clash), but which one should sit on _/dev/random_ and _/dev/urandom_? Debian's _alternatives system_ doesn't help here, because the translators may need different command line arguments.
+
+One idea is to have the _postinst_ instructions set the passive translator if there isn't already one set on the relevant node(s).
+
+## <a name="Short_Long_Description_Guideline"> Short/Long Description Guidelines </a>
+
+    [packagename]: Foo translator for [doing bar].
+    Foo is a GNU/Hurd translator which does [bar].
+
+## <a name="Miscellaneous"> Miscellaneous </a>
+
+There could / should be a meta package (or even more than one) that just depends e.g. on all installable translators, so that they'll conveniently find their way into the system by just installing that meta package.
 
 -- [[Main/MichaelBanck]] - 10 Mar 2006
-- 
cgit v1.2.3