Hi all, I also recently remarked a problem with the cs definition : I am always using the UTM projection, and if I try to force an UTM projection that is not in the right zone, it does not work. Id est, if I am close to the UTM18 zone, but in the UTM17 zone, and that I try to force the projection to UTM18 to be consistent with the rest of the caves system, my output remains with the UTM17 projection (at least, this is what is written in the header that I tweeked with Bruce's developments).
Cheers, Xavier De: "List for Therion users" <[email protected]> À: "List for Therion users" <[email protected]> Cc: "Bruce Mutton" <[email protected]> Envoyé: Lundi 4 Mars 2019 04:38:05 Objet: [Therion] tex outcsname variable broken It seems a problem with the outcsname token register has been introduced with release 5.4.3. Instead of containing the output coordinates system name, it now contains the output coordinates system code. As below, stepping through recent Therion releases… Version 5.4.2 creates this in my customised header; …as does therion 5.4.2+16a5e3e (2019-01-17) But 5.4.3 and all subsequent versions create this; Bruce _______________________________________________ Therion mailing list [email protected] https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list [email protected] https://mailman.speleo.sk/listinfo/therion
