TM->TMW and TMW->TM conversion in RTF is now supported. I've
noticed that formatting is mostly OK but sometimes gets bungled slightly. I tried everything I could think of, and now I'm passing the buck to Java's RTF support. TMW_RTF_TO_THDL_WYLIE (now misnamed) support TMW->TM conversion (but not TM->TMW). There is an automated test case for a TMW->TM conversion. I have full confidence in this conversion. Even the smallest glitch in the core functionality (not formatting) would surprise me.
This commit is contained in:
parent
bfacd6c998
commit
56d5ac7210
2 changed files with 2 additions and 1 deletions
|
@ -348,6 +348,7 @@
|
|||
<target name="compile-junit-tests" depends="init"
|
||||
description="compiles all JUnit test cases that can be compiled in the present CLASSPATH (NB that this distinction is just wishful thinking for now because we have such weak test coverage at this point)" >
|
||||
<mkdir dir="${junitbin}"/>
|
||||
<antcall target="create-timestamp-source-code"/> <!-- DLC NOW! The -run targets are mucking with this! It isn't fatal, but it should be fixed. -->
|
||||
<antcall target="our-internal-javac-task">
|
||||
<param name="mybin" value="${junitbin}"/>
|
||||
<param name="my.included.source.file"
|
||||
|
|
|
@ -34,7 +34,7 @@
|
|||
<!-- This creates output files TEST* in the Jskad/ directory. -->
|
||||
<target name="run-all-junit-tests"
|
||||
description="Assuming that compilation of appropriate classes has been done, this target runs all the JUnit tests in the project.">
|
||||
<junit fork="no" printsummary="yes" haltonfailure="yes" haltonerror="no">
|
||||
<junit fork="no" printsummary="yes" haltonfailure="no" haltonerror="no">
|
||||
<classpath>
|
||||
<pathelement location="${junitbin}"/>
|
||||
<path refid="entire.class.path"/>
|
||||
|
|
Loading…
Reference in a new issue