-----Original Message-----
From: R Smith
On 2017/12/19 8:37 PM, Tony Papadimitriou wrote:
A couple of questions about printf
1. Does it work with UTF-8? If so, how?
- Yes.
- Very nicely.
I'm using SQL v3.21 and UTF-8 does not work correctly. (Not from the
command line.)
I tried with latest trunk and it works fine. Hmmm.
Let's try with the precompiled Windows binary for v3.21.0
It works. Hmmm!
(...many, many trials later...)
Let's try with different default options.
Ta da!!!
When using the -column option (my own binary has this as default) the
problem shows up. With the official default of -list option the problem is
not there.
And, it happens with the latest trunk, also.
So, that looks like a bug.
2. Does it understand \n and \t? I put actual line breaks inside the
string >which is OK if run from script file but it won’t work with
one-liners on the >command-line.>
The \n, \t, \r etc. are really dependent on some factors (OS etc.).
Yes, I know all that. The question was if it understands them, not how they
might behave depending on OS.
When I use \t or \n I get actual \t and \n strings displayed instead of
tabbing and advancing line, respectively.
So, is there any way to advance to next line from a command line printf()?
Ryan
Thanks
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
