It does make sense. However, we already know that people want
tree conflicts to work with TortoiseSVN. Now, the Tortoise developers
could either invent their own human readable descriptions, or use an
API we provide (and which our command line client is using).

For consistency, I'd like to provide them with an API they can use,
IFF we decide that having our core libraries providing some form of
human readable representation of tree conflicts is a good idea.

So far I had assumed this was the case, but I don't mind reverting
that decision. In which case I'd favour moving the human readable
descriptions out of the core libraries entirely, into our command
line client -- libsvn_subr/cmdline.c might be an option.