There are subtle differences in which TFS are used. Some apply to protocol elements where the explicit values are defined in standards, where the text has all words capitalised, e.g., “Requested”, “Not Requested “. Some apply to protocol elements where there’s no such explicit definition, e.g., “Should be traced”, “Should not be traced”. (Or maybe it is, I don't know.). In all, it’s impossible to set a hard rule either way, so we leave it up to the authors to define the true_false_strings, and optionally provide them for general use.
Jaap > On 22 Feb 2026, at 04:27, Tamás Regős <[email protected]> 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 -- [email protected] To unsubscribe send an email to [email protected]
