What about a 'Data objec' or 'Spec object' which indicates which English method name corresponds to which french method name. This could be done by suppyling a sourceString which contains a CSV version of the method equivalences.
Then the DrGeoFigure may be generated by a simple script as
A generated method of a DrGeoFigureg object then sends the English method equivalent to a DrGeoSketch object.
This will allow to easily extend the number of translations by having translators to come up with a CSV list of method equivalents only. Translators do not need to be Smalltalk programmers.
What about a 'Data objec' or 'Spec object' which indicates which English method name corresponds to which french method name. This could be done by suppyling a sourceString which contains a CSV version of the method equivalences.
Then the DrGeoFigure may be generated by a simple script as
Object subclass: #DrGeoFigure leNames: 'drgeo' ames: '' Core-Script'
instanceVariab
classVariableN
poolDictionaries: ''
category: 'DrGeoII-
A generated method of a DrGeoFigureg object then sends the English method equivalent to a DrGeoSketch object.
This will allow to easily extend the number of translations by having translators to come up with a CSV list of method equivalents only. Translators do not need to be Smalltalk programmers.