grp@Unify.com (Greg Pasquariello) (05/15/91)
Can anyone in the know comment on if/how translation management might change with R5 widgets? I have run into a number of "situations" in parsing and merging translations that don't work quite as expected, and I'm now in a position where I need to determine how this will affect future implementations of software. Thanks for any information you can provide. -- --- Greg Pasquariello grp@unify.com Unify Corporation Be good and never poison people
swick@athena.mit.EDU (Ralph R. Swick) (05/15/91)
Can anyone in the know comment on if/how translation management might change
with R5 widgets?
We intend to make no changes to documented behavior, to fix a few places
where the R4 implementation did not match the documented behavior, to make
as few changes as possible to undocumented behavior when we believe the
undocumented behavior was correct and to make some desirable changes to
undocumented behavior that we believe no one should have been relying upon.
(How's that for a no-op answer? :-)
On the more practical side, Hewlett-Packard has donated a reimplementation
of the Translation Manager with substantial improvements in memory usage.
We are in the process of looking for other behavioral differences, both
to the documented semantics and to the undocumented semantics (of which,
unfortunately, the translation manager has many) and we expect to ship
this new implementation in R5.
I have run into a number of "situations" in parsing and
merging translations that don't work quite as expected,
Filing a bug report is the best way to bring these to our attention
and get an answer as to whether these are indeed implementation bugs
and whether or not you should rely on the behavior. A bug report is
also the best way to appraise us of the impact of possible changes
to unspecified behavior on existing applications.