Eric Blake wrote: > Be careful; the POSIX specification of '%.30s' does NOT work well with > multibyte characters; it is specified as: > ... > which means that it CAN and WILL corrupt output if the number of bytes > written falls in the middle of a multi-byte character.
Good point. Which leads me back to thinking that printing a tag first and then the filename second and letting it be as long as it needs to be without truncation is the best solution. But of course in the original application coming from a legacy environment the file names would never be multibyte. Bob
