Marko Rauhamaa <ma...@pacujo.net> writes:

> David Kastrup <d...@gnu.org>:
>
>> Marko Rauhamaa <ma...@pacujo.net> writes:
>>> That operation fails if you try to translate the snippets to strings
>>> before concatenation. Such concatenation operations are commonplace
>>> when dealing with filenames (eg, split(1)).
>>
>> split(1) does not "deal with filenames" when splitting, but the
>> individual files may be split inside of UTF-8 sequences.  See above.
>
> You probably cannot produce valid UTF-8 out of invalid UTF-8 snippets
> with split(1). However split(1) does form filenames out of its arguments
> by concatenation:
>
>     split --additional-suffix=suffix file prefix
>
> produces these kinds of filenames:
>
>     <prefix><ordinal><suffix>

I don't really get your point here.  Why would you start with invalid
UTF-8 sequences in the filenames?

-- 
David Kastrup

Reply via email to