<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Andrew<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>Thanks for those revised input/output file instructions –
makes perfect sense now.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>> Perhaps the plan
and elevation scraps should be forced (or at least <o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>> have the option)to
inherit the map suffixes entered on the Data TAB <o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>> (and then the
specific plan, elevation and section suffixes entered on <o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>> the plan and elevation
TABs).<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>> <o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>> This would ensure
better consistency and ready recognition by the <o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>> human user of the
relationship of particular scraps </span></font><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>–</span></font><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
maps </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>–</span></font><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'> files.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>>Sorry not sure what you
mean, do you mean that they all should be NewPassageSuffix.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>>Can
you give an example, this is different from what I do</span></font><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>The approach I am
trying to enforce is that each object inherits the name of it’s parent,
and any suffixes that might have been appended to the parent (or
grandparent). Also that each object name describes quite explicitly and
unambiguously what it contains (but not overly verbose). Pretty close to what
Topparser encourages already.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>eg<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Survey name: 404-Quackery<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Associated maps are
therefore named;<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>404-QuackeryPlan<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>404-QuackeryElevEXT<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>404-QuackeryElev290<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Etc<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Topparser
encourages this at present.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><img width=366 height=286 id="_x0000_i1027"
src="cid:image003.jpg@01CE8C94.84968AF0"><o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>(A somewhat
unrelated observation: Maps do not need to be children of the surveys they are
based on, but the way Topparser currently creates them they are. Therion
does allow them to be outside of the ‘survey’
‘endsurvey’ block, and indeed outside of the survey.th file
altogether. This is another topic however, but it could add complexity to
Topparser in due course. For now it is easy enough for the user to move the map
definitions to another file if they so wish.)<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Children of the
maps<font color=navy><span style='color:navy'> (</span></font>scraps<font
color=navy><span style='color:navy'>)</span></font> are therefore named;<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>404-QuackeryPlan-s1,
404-QuackeryPlan-x1<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>404-QuackeryElevEXT-s1,
404-QuackeryElevEXT-x<font color=navy><span style='color:navy'>p</span></font>1,
404-QuackeryElevEXT-xv1<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>All the above can
be achieved with Topparser at present, but you have to duplicate part of the
suffix as in these screen dumps.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><img width=332 height=211 id="_x0000_i1029"
src="cid:image004.jpg@01CE8C94.84968AF0"><img width=349 height=211
id="_x0000_i1031" src="cid:image005.jpg@01CE8C94.84968AF0"><o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>The current implementation
cannot mimic the type of inheritance I would like for projected elevations
however;<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>404-QuackeryElev290-s1
is what I would like, but;<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><img width=342 height=204 id="_x0000_i1037"
src="cid:image008.jpg@01CE8C94.84968AF0"><o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>The above produces;<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>404-QuakeryElev-s290_1<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> which is at
odds with the rest of the object naming.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>So in summary,
Topparser in general allows scraps that are not named the same as the th2 file
they are inside of. While this might allow for more abbreviated scrap
names it is not what the Therion wiki recommends (sure I’ve seen it
somewhere :) ).<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>This can be
compensated for as in the examples above in all cases except for projected
elevations.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>A minor thing that
is easy for the user to overwrite each time – but worth considering.<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'>Bruce<o:p></o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoAutoSig style='margin:0cm;margin-bottom:.0001pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>