path: root/hurd/translator.mdwn
diff options
authorThomas Schwinge <>2010-07-23 21:36:51 +0200
committerThomas Schwinge <>2010-07-23 21:40:39 +0200
commite4bc6001d92438b7733aae57b394f3c18bd0f9be (patch)
tree40eeca1edc9d0cab7498cb2bad0eab9cded84a1a /hurd/translator.mdwn
parent399aaf28e538fc1c6f5adda3cf90cc6303b5721b (diff)
hurd/translator: Another stance / explanation about what *to translate* means.
Diffstat (limited to 'hurd/translator.mdwn')
1 files changed, 7 insertions, 1 deletions
diff --git a/hurd/translator.mdwn b/hurd/translator.mdwn
index 44ba4dff..dc3fd256 100644
--- a/hurd/translator.mdwn
+++ b/hurd/translator.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2007, 2008, 2009 Free Software Foundation,
+[[!meta copyright="Copyright © 2007, 2008, 2009, 2010 Free Software Foundation,
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -18,6 +18,12 @@ and [[pfinet]]) and thus translates object invocations
into calls appropriate for the backing store
(e.g., ext2 file system, nfs server, etc.).
+Another way of putting it is that it translates from one representation of a
+data structure into another representation, for example from the on-disk
+[[ext2|ext2fs]] data layout to a traditional file system hierarchy, or from a
+XML file to a virtual hierarchical manifestation. This translation can be a
+bidirectional process, but it need not be.
A translator is usually registered with a specific file system node by using
the [[`settrans`|settrans]] command.