Talk:Terminal control/Unicode output: Difference between revisions

From Rosetta Code
Content added Content deleted
Line 5: Line 5:


::Thanks Mark. --[[User:Paddy3118|Paddy3118]] 16:05, 11 September 2011 (UTC)
::Thanks Mark. --[[User:Paddy3118|Paddy3118]] 16:05, 11 September 2011 (UTC)

== Er, "Terminal supports"? ==

I can run <code>xterm +u8</code> with UTF-8 locale, and both current awk and shell solutions output garbage. What does it mean, "terminal supports unicode"? The ZX spectrum basic solution doesn't even make sense: can you display more than 256 different characters on screen at once? If not, what good is this "unicode support"? --[[User:Ledrug|Ledrug]] 03:12, 12 September 2011 (UTC)

Revision as of 03:12, 12 September 2011

Unix shell embedding Awk?

Surely you can check an environment variables value in the shell, without the need to call Awk. As it stands, it doesn't seem to be a good example of using the Unix shell. --Paddy3118 07:59, 11 September 2011 (UTC)

We cannot check for substrings on a Bourne shell, so we have to use AWK. Other shell implementation may not need to do this of course. Markhobley 08:02, 11 September 2011 (UTC)
Actually, it looks like you can match substrings by using the switch command. If this works I will try and rewrite this to get rid of awk. Markhobley 08:20, 11 September 2011 (UTC)
Thanks Mark. --Paddy3118 16:05, 11 September 2011 (UTC)

Er, "Terminal supports"?

I can run xterm +u8 with UTF-8 locale, and both current awk and shell solutions output garbage. What does it mean, "terminal supports unicode"? The ZX spectrum basic solution doesn't even make sense: can you display more than 256 different characters on screen at once? If not, what good is this "unicode support"? --Ledrug 03:12, 12 September 2011 (UTC)