Re: batch processing and 5.17.16
Good point, batch converter should perhaps take a path to the pcc rather than the campaign tag, worth a JIRA on that.
Alternatively or even additionally, as the datasets are defined in the .pcg itself, worth JIRA'ing a request to make the batch converter determine the sources itself and autoload so you don't *have* to specify them...
--- In email@example.com, Susan Dittmar <Susan.Dittmar@...> wrote:
> Dear Dave,
> Quoting FerretDave (ferret.griffin@...):
> > Just a recommendation, try to avoid using punctuation in names - for
> > datasets, files or just about anything really, it helps avoid all sorts
> > of odd issues with batch processing etc.
> I completely agree with you - except that at the time I created my campaign
> file, it looked like the contents of the CAMPAIGN: tag in a pcc file would
> only be output as an abitrary text in program and on the character sheet.
> It for sure was not _my_ idea to have that text (instead of a filename) as
> argument to the -m switch of PCGen as indicated in
> > I myself have moved on from limiting myself to actual 8.3 filenames
> > nowadays, but I still avoid spaces/punctuation in filenames, regardless
> > of what the OS may allow, if there's any chance I'm going to refer to
> > them from a script and it really does help cut down the confusion :-)
> If it were a filename, I would call it my own fault and pay the price
> without bitching ;-)
> > As you're using linux, you have the tools (sed!) to easily go through
> > your 500 NPC files and change the detail on each and every one and change
> > the data set name...
> I will if I must. But as this text is output in places where it clearly is
> meant for humans (contrary to filenames which are for computers), I would
> prefer another solution.