'Bypass' injection check?

Well...
As I said, I was told I should secure this project by protecting it from injections.
At this point, the protect-function-code was offered to be copied.

Why the pipe is 'dangerous', idk...
So far, it has not been of a big issue, but of course when printing "usage" string - as they are used to be presented - it raises an issue.

Well I could work around this, by removing the 'doubles' (aka long and short paramenters for the same option), thus removing the need to use the pipe symbol in 'usage' strings.

Yes, I did expect something different from latin1.
As I was under the impression it would be 8bit and thus allow the 179 or 221 ASCII codes of alternative symbols to the pipe char, which you said to be more than 8 bit.
Because the 179 and 221 chars are supposed to be a similar chars to the pipe, within the ascii standart of 1983.
Well... one of them them is identical anyway... (as in, it was actualy used instead of the 124 pipe)

Yes, the pipe handling 'should' be irrelevant as it 'just' needs to pass the protect function, as soon that is done, the output will be as I want/expect it. (apart from the fact that I'll even use | printe -1 -- when it otherwise works.

It shoud look similar to this (the splitting needs adjustment though):

[~/prjs/SWARM] 1 $ cfg.edit | printe --
# | Usage: cfg.edit [-T OR --title 'Custom Title'] [--option                                                      | #
# | OPTNAME [--values 'val1 val2 ...'] [--default val1]] FILE1                                                    | #
# | [FILE2 ...]                                                                                                   | #

So, we see, as soon no pipe char is used (but OR instead ^^), everything works as expected (again, apart from the split fine tuning)...

So I dare say, whatever the printe function is (past the protect call), is not relevant.
But if you think it might be, I had posted it a while back (printe is the pipe wrapper for these commands - as you have had seen in the pipe-related link):

But.. I might be wrong.. so here we go:

printe () 
{ 
    swarm.protect "$FUNCNAME" "${@}" && exit 1;
    local MODE="none";
    case "$1" in 
        "-1" | "-2")
            MODE="${1/-}";
            shift
        ;;
        *)
            MODE="normal"
        ;;
    esac;
    [[ "normal" == "$MODE" ]] && [[ "-" != "$1" ]] && [[ "--" != "$1" ]] && MODE=${#@};
    case "$1" in 
        "--" | "-")
            shift;
            case "$MODE" in 
                "2")
                    while read LEFT; do
                        read RIGHT;
                        printe "$LEFT" "" "$RIGHT";
                    done;
                    return 0
                ;;
                "1")
                    while read LEFT; do
                        printe "$LEFT";
                    done;
                    return 0
                ;;
                *)
                    while read LEFT; do
                        read CENTER;
                        read RIGHT;
                        printe "$LEFT" "$CENTER" "$RIGHT";
                    done;
                    return 0
                ;;
            esac
        ;;
    esac;
    case "$MODE" in 
        "0")
            swarm.print.border -e;
            swarm.print.text -e "" "" ""
        ;;
        "1")
            swarm.print.border -e;
            swarm.print.text -e "$1" "" ""
        ;;
        "2")
            swarm.print.border -e;
            swarm.print.text -e "$1" "" "$2"
        ;;
        "3")
            swarm.print.border -e;
            swarm.print.text -e "$1" "$2" "$3"
        ;;
    esac;
    $PRINTF "$posEND\n"
}