Thanks Gino, changes now merged and submitted to svn/trunk.
On Fri, Jun 19, 2009 at 2:55 PM, Gino van den Bergen<[email protected]> wrote: > AFAICS, OSG's OBJ loader correctly handles backslash-newlines that are used > for continuation of lines. However, I recently ran into a problem with OBJs > that where converted from another source using Right Hemisphere Deep > Exploration. In these OBJs newlines are escaped in the following way: > > f 15939/9999/16177 15941/10000/16178 15940/10001/16179\ > 15938/10002/16180 > > In the OBJ loader the newline would be interpreted as follows > > f 15939/9999/16177 15941/10000/16178 15940/10001/1617915938/10002/16180 > > However, for correctly loading the model it should be interpreted as > > f 15939/9999/16177 15941/10000/16178 15940/10001/16179 15938/10002/16180 > > Thus, the escaped newline should be interpreted as a space. > > I tried to lookup what the correct interpretation for a backslash-newline > was in the OBJ spec but did not find anything useful. Nevertheless, my > suggestion would be to adopt replacing the escaped newline by a space in > order to avoid problems as stated above. I cannot imagine a meaningful usage > of a newline within a numerical literal so I do not foresee cases where > replacing a backslash-newline by a space would be harmful. The fixed obj.cpp > is zipped and attached to this mail. > > Kind regards, > > Gino > > > > > > > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
