[Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx>]

Not sure, but I suspect that they have been added with whatever capitalization they had in whatever spec they were first added from.

I would be sympathetic to a dissector author whose protocol matches except for capitalization and really wants it to appear as in their protocol specification -  tools/check_tfs.py warns where shared entries could have been used, but it distinguishes matches that are exact or where capitalization differs.

But I don't have strong feelings about this either way - I probably have made some dissectors use the common version with different capitalization in some cases (particularly where there is not actively working on it).

Martin  

On Sun, Feb 22, 2026 at 3:27 AM Tamás Regős <regost@xxxxxxxxx> wrote:

Hello Dev team,

It seems epan/tfs.c is a bit inconsistent.

Some of the true_false_string have each word capitalized while others have the first word only.

{ "Restricted", "Not restricted" }

{ "Not restricted", "Restricted" }

{ "Supported", "Not supported" }

{ "Not Supported", "Supported" }

...

{ "Allowed", "Not Allowed" }

{ "Not Allowed", "Allowed" }

{ "Reliable", "Not Reliable" }

{ "Requested", "Not Requested" }

...

Should these be consistent instead (all or none with title case)?

Thank you.

Regards,

Tamas

_______________________________________________
Wireshark-dev mailing list -- wireshark-dev@xxxxxxxxxxxxx
To unsubscribe send an email to wireshark-dev-leave@xxxxxxxxxxxxx