kvid

> It would also be great if the YAML had the ability to specify the requested outputs. I agree, but I would like to be able to override such YAML...

- With the current (master branch) version, you can add notes to the cable that describes the glands. - With the current [dev branch](https://github.com/formatc1702/WireViz/tree/dev) (that probably soon will become a...

This seems to be a duplication of #212 from last year that also includes my more recent [work-around suggestion](https://github.com/formatc1702/WireViz/issues/212#issuecomment-1030236831). If that old issue also covers your use case, then I...

These ideas you present, are great! 👍 I just have a few comments about some details. > German color codes (rt) By accepting German codes as input, I assume requests...

> > For example the default green is far to bright in my opinion. Also when having striped / banded colors the defaulted ones might not go well with each...

We need clear rules on how to handle such characters when generating the different output formats, as they have different limitations: - `.bom.tsv` does not support TAB, CR or LF...

- Different gauges per cable could easily be specified as an optional list of gauges (one for each wire), but to show them in the diagram, a new row for...

The two feature requests in this issue are independent and can be implemented independently of each other - maybe in two different PRs, but @formatc1702 wants to finish and merge...

I would also like to get more feed-back on how the new features should look like. The gauges feature is the easiest to implement, and should perhaps be done first....

@Halfwalker wrote: > I kind of like the summary of gauges - it serves as a checkpoint. Handy to verify things, especially if you have a bundle of a LOT...