<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:CMTI12;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:CMR12;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:CMTT12;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.fontstyle01
{mso-style-name:fontstyle01;
font-family:"CMTT12",serif;
color:#2E3092;
font-weight:normal;
font-style:normal;}
span.fontstyle21
{mso-style-name:fontstyle21;
font-family:"CMR12",serif;
color:black;
font-weight:normal;
font-style:normal;}
span.fontstyle31
{mso-style-name:fontstyle31;
font-family:"CMTI12",serif;
color:black;
font-weight:normal;
font-style:italic;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-NZ link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Both (all?) approaches discussed have merit, and could be considered ‘correct’ in varying circumstances.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>We already have a <b>revise</b> statement and a <b>person-rename</b> statement, so lets figure out if they can be used ‘as is’ for Benedikts purposes, and if not if there is an acceptable change that could be made. I like the idea of merging multiple persons in ‘club groups’ as was suggested earlier, as for large overview maps this makes the header a smaller more manageable size, without the need for manual edits.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>I have used <b>revise</b> to change station-names at compile time, where scraps are drawn spanning multiple surveys and -station-names have been used in the original centrelines. <span lang=FR>Ie <a href="https://therion.speleo.sk/wiki/paperless?s%5b%5d=revise">https://therion.speleo.sk/wiki/paperless?s[]=revise</a><o:p></o:p></span></p><p class=MsoPlainText style='margin-left:36.0pt'><span lang=FR><o:p> </o:p></span></p><p class=MsoPlainText style='margin-left:36.0pt'>Also to reuse a projected elevation scrap as an extended elevation (where the projection angle is perpendicular to the passage).<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>I have explored it’s use when creating multiple extended elevations of different configuration (left, right, hide etc) from the same centreline data (forget if I ended up using revise for this or not).<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>It can be used to alter map definitions at compile time (according to the Therion Book).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>So there is already the generic precedent and capability.<o:p></o:p></p><p class=MsoPlainText>There must be many other possible uses.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>From the Therion Book…<o:p></o:p></p><p class=MsoPlainText><b><span lang=FR>revise<o:p></o:p></span></b></p><p class=MsoPlainText>Description: This command is used to set or change properties of an already existing object.<o:p></o:p></p><p class=MsoPlainText>Syntax: The syntax of this command for object created with “single line” command is <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText style='text-indent:36.0pt'><span class=fontstyle01><span style='font-size:12.0pt'>revise id [-option1 value1 -option2 value2 ...]<o:p></o:p></span></span></p><p class=MsoPlainText style='margin-left:36.0pt'><span style='font-family:"CMTT12",serif;color:#2E3092'><o:p> </o:p></span></p><p class=MsoPlainText><span class=fontstyle21><span style='font-size:12.0pt'>For objects created with “multi line” commands is syntax following<o:p></o:p></span></span></p><p class=MsoPlainText style='margin-left:36.0pt'><span style='font-family:"CMR12",serif;color:black'><br></span><span class=fontstyle01><span style='font-size:12.0pt'>revise id [-option1 value1 -option2 value2 ...]</span></span><span style='font-family:"CMTT12",serif;color:#2E3092'><br></span><span class=fontstyle01><span style='font-size:12.0pt'>...</span></span><span style='font-family:"CMTT12",serif;color:#2E3092'><br></span><span class=fontstyle01><span style='font-size:12.0pt'>optionX valueX</span></span><span style='font-family:"CMTT12",serif;color:#2E3092'><br></span><span class=fontstyle01><span style='font-size:12.0pt'>data</span></span><span style='font-family:"CMTT12",serif;color:#2E3092'><br></span><span class=fontstyle01><span style='font-size:12.0pt'>...</span></span><span style='font-family:"CMTT12",serif;color:#2E3092'><br></span><span class=fontstyle01><span style='font-size:12.0pt'>endrevise<o:p></o:p></span></span></p><p class=MsoPlainText><span style='font-family:"CMTT12",serif;color:#2E3092'><br></span><span class=fontstyle31><span style='font-size:12.0pt'>Context: </span></span><span class=fontstyle21><span style='font-size:12.0pt'>all</span></span><span style='font-family:"CMR12",serif;color:black'><br></span><span class=fontstyle31><span style='font-size:12.0pt'>Arguments:</span></span><i><span style='font-family:"CMTI12",serif;color:black'><br></span></i><span class=fontstyle21><span style='font-size:12.0pt'>The id stands for object identifer (the id of an object you want to revise must always be specified). <o:p></o:p></span></span></p><p class=MsoPlainText><span class=fontstyle21><span style='font-size:12.0pt'><o:p> </o:p></span></span></p><p class=MsoPlainText>Bruce<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-US style='mso-fareast-language:EN-NZ'>-----Original Message-----<br>From: Therion [mailto:therion-bounces@speleo.sk] On Behalf Of Wookey via Therion<br>Sent: Tuesday, 7 March 2017 1:58 AM<br>To: Benedikt Hallinger via Therion <therion@speleo.sk><br>Cc: Wookey <wookey@wookware.org><br>Subject: Re: [Therion] Revise command: how to remove persons later on</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 2017-03-05 19:30 +0200, Benedikt Hallinger via Therion wrote:<o:p></o:p></p><p class=MsoPlainText>> The same reason like already told in this thread: the data should <o:p></o:p></p><p class=MsoPlainText>> reflect otherwise recorded data.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Right, but in this case they didn't actually turn up, so how is it correct to leave them as listed on the survey team?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I, too, like to keep notes original, but when they are provably wrong they are changed (usually with a comment explaining the change from the original notes). This happens regularly for instrument readings, and sometimes for station conenctions. It can happen for team members too.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Unless someone wants to propose a general 'revised notes' command, I don't think it makes sense to provide this for team members, but not readings, or indeed anything else.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I can see that marking data as 'revised from original notes' might actually be useful (because that effectively makes it possible to show the 'thisa was revised' comments in some kind of UI).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Wookey<o:p></o:p></p><p class=MsoPlainText>--<o:p></o:p></p><p class=MsoPlainText>Principal hats: Linaro, Debian, Wookware, ARM <a href="http://wookware.org/"><span style='color:windowtext;text-decoration:none'>http://wookware.org/</span></a><o:p></o:p></p></div></body></html>