Thanks for help and claryfing info.
I'll try to work with that, hopefully reaching desired result. However, document version recognizable by Windows would be the best.
Search found 4 matches
- Fri Aug 09, 2019 12:47 pm
- Forum: Help & Manual 7 Forum
- Topic: Project properties
- Replies: 2
- Views: 1192
- Fri Aug 09, 2019 12:39 pm
- Forum: Help & Manual 7 Forum
- Topic: Automated export using Powershell
- Replies: 2
- Views: 1140
Re: Automated export using Powershell
Hi Tim,
yes, I am quite familiar with it, PS is just my personal preference.
This script solves compatibility problem occured during processing CMD switches in PS (unavailability to read variables after making PS dumber with --% ) at first.
Maybe somebody will find this useful.
yes, I am quite familiar with it, PS is just my personal preference.
This script solves compatibility problem occured during processing CMD switches in PS (unavailability to read variables after making PS dumber with --% ) at first.
Maybe somebody will find this useful.
- Fri Aug 09, 2019 8:31 am
- Forum: Help & Manual 7 Forum
- Topic: Project properties
- Replies: 2
- Views: 1192
Project properties
Hi guys, I'd like to ask if project properties, especially Title & Copyright, are accessible as metadata (if yes, how?), or these are just text variables. Tried to retrieve metadata from PDF, but it seems information like document version are not stored here. Looks like it could be done by parsi...
- Fri Aug 09, 2019 8:21 am
- Forum: Help & Manual 7 Forum
- Topic: Automated export using Powershell
- Replies: 2
- Views: 1140
Automated export using Powershell
Hi guys, maybe this Powershell script will be helpful, it saves me a lot of time. I personally use it for automated export of multiple projects included in specific directory into one specific output format. PS $helpman = 'enter path to Help+Manual .exe file' $runPath = 'enter complete path for dire...