mirror/guile
mirror/guile
1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-06-11 22:31:12 +02:00
Code Activity

*** empty log message ***

Browse source
This commit is contained in:
Mikael Djurfeldt 2000-08-13 04:47:26 +00:00
parent f587dec1ba
commit 7f43f900ed
1 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

18
devel/translation/langtools.text
View file

@ -1,13 +1,13 @@
* Introduction
Version: $Id: langtools.text,v 1.4 2000-08-13 04:16:18 mdj Exp $
Version: $Id: langtools.text,v 1.5 2000-08-13 04:47:26 mdj Exp $
This is a proposal for how Guile could interface with language
translators. It will be posted on the Guile list and revised for some
short time (days rather than weeks) before being implemented.
The document can be found in the CVS repository as
guile-core/devel/translation/lantools.text. All Guile developers are
guile-core/devel/translation/langtools.text. All Guile developers are
welcome to modify and extend it according to the ongoing discussion
using CVS.
@ -279,11 +279,11 @@ uses the sharp comma extension specified by SRFI-10. The read
constructor is simply the last symbol in the long language name (which
is usually the same as the short language name).
** Example1
** Example 1
Characters have the syntax in Scheme and in ctax. Lists currently
have syntax in Scheme but lack ctax syntax. Enums have syntax in ctax
but lack Scheme syntax.
have syntax in Scheme but lack ctax syntax. Ctax doesn't have a
datatype "enum", but we pretend it has for this example.
The following table now shows the syntax used for reading and writing
these expressions in module A using the language scheme, and module B
@ -298,7 +298,7 @@ lists (1 2 3) #scheme (1 2 3)
enums #,(ctax ENUM) ENUM
** Example2
** Example 2
A user is typing expressions in a ctax module which imports the
bindings x and y from the module `(foo)':
@ -524,13 +524,13 @@ they will be automatically used by the error reporting machinery.
** Implement the above proposal.
* Add new field `reader' and `translator' to all module objects
** Add new field `reader' and `translator' to all module objects
Make sure they are initialized when a language is specified.
* Use `untranslate' during error handling.
** Use `untranslate' during error handling.
* Implement the use of arg 5 to scm-error
** Implement the use of arg 5 to scm-error
(specified in "Errors during translation")