A Miski channel is identified by user and subject within the user's subject space. Since the subject has to be written in some language, and the subject description is intended to be self-contained and unambiguous, a language code should be included in the channel description. This does not have to describe the precise language variant, it should rather specify the language precisely enough for the subject description to be unambiguous. The same language code can be taken as a guide as to what language the messages in that channel are going to be written in. Character Sets Character sets are another source of trouble.
Different languages have to be written in different character seats.
The interpretation of the octets depends on the URL scheme. In the White Paper I suggest that Miski URL's contain user ID, language code and subject.