Results for disregarding translation from Korean to English

the optional parameter mode determines the unit length. if it's 0 or omitted the default unit as specified for the page is used. otherwise the coordinates are measured in postscript points disregarding the current unit.
otherwise the coordinates are measured in postscript points disregarding the current unit.

saying that hw_pipedocument() and hw_gettext() do the link insertion automatically is not as simple as it sounds. inserting links implies a certain hierarchy of the documents. on a web server this is given by the file system, but hyperwave has its own hierarchy and names do not reflect the position of an object in that hierarchy. therefore creation of links first of all requires a mapping from the hyperwave hierarchy and namespace into a web hierarchy respective web namespace. the fundamental difference between hyperwave and the web is the clear distinction between names and hierarchy in hyperwave. the name does not contain any information about the objects position in the hierarchy. in the web the name also contains the information on where the object is located in the hierarchy. this leads to two possibles ways of mapping. either the hyperwave hierarchy and name of the hyperwave object is reflected in the url or the name only. to make things simple the second approach is used. hyperwave object with name 'my_object' is mapped to 'http://host/my_object' disregarding where it resides in the hyperwave hierarchy. an object with name 'parent/my_object' could be the child of 'my_object' in the hyperwave hierarchy, though in a web namespace it appears to be just the opposite and the user might get confused. this can only be prevented by selecting reasonable object names.
each object record has native a string representation with each name / value pair separated by a newline.