You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I think it would be useful to allow an optional comment (or notes) column, just after function, which would enable documenting a little bit better what a specific code does.
For example, a Panasonic code for INPUT TV could be documented as "Switches input to TV, or toggles tuner among analog/digital/etc.".
I have documented/clarified a number of codes over the years and I would like to be able to contribute this documentation to this project. What do you think? If you like this idea, I can then submit some PRs.
The text was updated successfully, but these errors were encountered:
The current (CSV) format has a number of shortcomings; the absence of a comment field is just one. I have written it down as #58, together with an alternative (Girr). This would be a systematic solution.
Hi. I think it would be useful to allow an optional
comment
(ornotes
) column, just afterfunction
, which would enable documenting a little bit better what a specific code does.For example, a Panasonic code for
INPUT TV
could be documented as "Switches input to TV, or toggles tuner among analog/digital/etc.".I have documented/clarified a number of codes over the years and I would like to be able to contribute this documentation to this project. What do you think? If you like this idea, I can then submit some PRs.
The text was updated successfully, but these errors were encountered: