Skip to content

Trans performers and the {performers} filename replacement. #292

@BiAndNerdy

Description

@BiAndNerdy

Currently, the {performers} filename tag/replacement does cis-gendered female performers only. Can that include trans-females as well?

My logic says it CAN be added to {performers} without pissing people off because they won't have trans vids anyway. Trans-positive people who do have those vids would almost certainly want female and trans performers listed if choosing {performers} over {all_performers} which includes male.

I don't have a problem with a separate {transf_performers} as long as this example would work:

[{site}] - {date} - {name} - {transf_performers} {performers}.{ext}

without adding that extra space when NO transf_perfomers are found. I have seen this done in other programs by adding the separator to the tag like this:

[{site - }]{date - }{name - }{transf_performers, }{performers}.{ext}

That way if any field is blank, both the placeholder/field AND the separator are left out of the filename. Either way it'd be cool to have that ability.

That's a big ask I know.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions