[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Summary (Re: A system for localizing documentation strings)
From: |
Davis Herring |
Subject: |
Re: Summary (Re: A system for localizing documentation strings) |
Date: |
Wed, 1 Aug 2007 11:11:21 -0700 (PDT) |
User-agent: |
SquirrelMail/1.4.8-6.el3.2lanl |
> What matters is that the coder has easy access to the translation
> database in a way or another _during_ the coding process without
> having to refer to a separate file.
Would it count as close enough to "without having to refer" if access to
the separate file were automated? Go to function (perhaps with
`find-function'), then invoke a hypothetical M-x find-doc-translations
(which would prompt for a function but default to the one at point) to go
to its bank of docstrings? This would be completely non-intrusive, and
trivial to implement.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
- Re: Summary (Re: A system for localizing documentation strings),
Davis Herring <=