Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We don't handle common TELNET codes #32

Closed
A9G-Data-Droid opened this issue May 11, 2018 · 1 comment
Closed

We don't handle common TELNET codes #32

A9G-Data-Droid opened this issue May 11, 2018 · 1 comment

Comments

@A9G-Data-Droid
Copy link

The following codes should be handled instead of treated like printable characters.

From RFC854:

     BELL (BEL)              7      Produces an audible or
                                    visible signal (which does
                                    NOT move the print head).
     Back Space (BS)         8      Moves the print head one
                                    character position towards
                                    the left margin.
     Horizontal Tab (HT)     9      Moves the printer to the
                                    next horizontal tab stop.
                                    It remains unspecified how
                                    either party determines or
                                    establishes where such tab
                                    stops are located.
     Vertical Tab (VT)       11     Moves the printer to the
                                    next vertical tab stop.  It
                                    remains unspecified how
                                    either party determines or
                                    establishes where such tab
                                    stops are located.
     Form Feed (FF)          12     Moves the printer to the top
                                    of the next page, keeping
                                    the same horizontal position.

http://www.rfc-editor.org/rfc/rfc854.txt

I have a solution that I will propose in an upcoming Pull Request.

@9swampy
Copy link
Owner

9swampy commented Aug 18, 2022

Merged in the release 0.9.1 I've just pushed to Nuget.

Any problems, shout.

@9swampy 9swampy closed this as completed Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants