<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=utf-8"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi Omri<o:p></o:p></p><p class=MsoNormal>These files are part of my ‘new project’ template, so they rea ready to go, as is (provided you have a similar folder layout to what I use). For me a project is usually a catchment or small caving region. Of course within that there are individual caves, so these files are more or less ‘one for each cave’. Except for the zipped files, which are ‘one for the project’.<o:p></o:p></p><p class=MsoNormal>The only change I make when I bring these into use is to find and replace each instance of ‘NameOfCave’ and change it to whatever the ‘shortcode’ name of the cave or catchment is. ie only the thconfig file.<o:p></o:p></p><p class=MsoNormal>All of these layout files are referenced (input) in the thconfig file.<o:p></o:p></p><p class=MsoNormal>From then on, any of the layout definitions can be invoked at will (using copy statement).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So it is more like your second statement below.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In case you are interested, I have included a default project readme file. It is an attempt to ensure all contributors to a particular mapping project are pulling the donkey (all of the donkeys) in the same direction. The data arrangement suggested is the only one that ticks all of the boxes for me, but it is far from universally accepted outside my circle of influence. Other arrangements are perfectly valid.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bruce<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> עמרי גסטר <omrigas@gmail.com> <br><b>Sent:</b> Tuesday, 11 June 2019 06:27<br><b>To:</b> bruce@tomo.co.nz<br><b>Subject:</b> Re: [Therion] code for Map layout<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I need to separate each layout to a different file and then call it with the copy command right?<o:p></o:p></p><div><p class=MsoNormal>or can I specify the file name and then call a specific layout from the file?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Mon, Jun 10, 2019 at 12:18 AM Bruce Mutton <<a href="mailto:bruce@tomo.co.nz" target="_blank">bruce@tomo.co.nz</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Omri<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Here is how I do it. My aim is to have it modular and flexible, so it is easy to get many types of pdf output from the same project, either simultaneously or with minimal easy edits between compiles. Refer attached. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Quite a lot of experimental noise in there, particularly in LayoutStandards.thc, but you should find something of use.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Some probably outdated explanatory information here <a href="https://therion.speleo.sk/wiki/templates" target="_blank">https://therion.speleo.sk/wiki/templates</a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>And here <a href="https://therion.speleo.sk/wiki/bds" target="_blank">https://therion.speleo.sk/wiki/bds</a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> Bruce<o:p></o:p></p></div></div></blockquote></div></blockquote></div></div></body></html>