CR 1099, documentation updated
When using AirPrint for a transparent print job, a full 80-character line that ends in a carriage return/line feed pair (CRLF) is counted as two lines, even though it prints as one. This throws off the page length counter, causing the print job to feed a new page before it’s needed.
TinyTERM ITX 2 and TinyTERM Pro for iOS both convert all Ctrl-J characters (ASCII 10) sent from the on-screen keyboard to Ctrl-M (ASCII 13) before sending them to the host. This change was made deliberately for customers who prefer the standard iPad keyboard. However, there is no way to revert this behavior if the ^J character is needed.
CR 1101, fixed in March 2013 releases
In TinyTERM Pro for iPhone, use the keyboard scan key to scan a bar code in landscape mode. On returning to TinyTERM Pro, the text size is at maximum. This happens with any other function that resets the keyboard and display also.
TinyTERM ITX 3270 for iOS does not currently include code page support. Century Software, Inc., has received a request to add multinational code page support, in particular German.
When using VT-series emulations on the new iPad (3rd or 4th generation) double-height characters are drawn in the wrong position. This does not affect the original iPad, iPad 2, iPhone or iPod Touch.
December 27th, 2012
No TinyTERM ITX product currently uses Siri for text dictation. Siri is very good at interpreting natural language. However, a typical shell prompt does not accept standard text. Adding Siri support to TinyTERM will require the ability to parse commands along these lines:
ls -lR | grep .obj | more
No TinyTERM ITX product has a user-driven clear screen capability at present. The host system must clear the screen. Century Software has received a request to add an option to clear the screen on demand.
All TinyTERM for iOS products support the creation of custom keyboard layouts. When creating a custom layout, the keyboard key at the beginning of a row sets the default height value for the entire row. As such, using the
keyHeight argument in the definition of the first key in a row changes the height for all subsequent keys. This causes display problems with the keyboard: either rows that are too short, or blank rows next to keys that are supposed to overlap the next row instead.
The workaround is to insert a thin blank key of standard height at the beginning of the row:
TinyTERM versions 4.8.0 (February 2013) and higher are fully supported on Windows 8. However, TinyTERM must run in the Desktop interface. It is not enabled for the Metro interface at this writing.
TinyTERM does not currently run on Windows RT. The CPUs used for the RT platform do not support instruction sets required by TinyTERM for Windows.