FUNICODE: Copy and paste exact Fonts not only content on the internet. Open message to Unicode Consortium

javascript's picture

Unicode has allowed codes for each letter in a language though on the internet, fonts cannot be copied and pasted similar to content. Thus I propose that you should implement or request others in your group to develop the FUNICODE (Font and Unicode) feature allowing copying and pasting of the exact fonts and not only content on the internet.


oldnick's picture

In other words, built-in font piracy? KKKKKKKKKrazy...

quadibloc's picture

Not necessarily. Perhaps only an identifier for the fond would be copied and pasted.

In a word processor, you can copy and paste text and preserve things like italics and boldface - and changes of typeface. Copying from a web browser into a word processor loses style information.

This is a technical issue in how browsers, which allow text on web sites to be selected, present the text to the Clipboard. It does not require the Unicode Consortium to get involved. And it would not involve copying the font.

oldnick's picture

I think the exact fonts means what it says; in other words, built-in font piracy...k?

quadibloc's picture

I realized that I was mistaken as well when I saw the other thread about "monopoly". It isn't a monopoly because font makers want to get paid.

John Hudson's picture

It does not require the Unicode Consortium to get involved.

Indeed, it has nothing to do with Unicode, which is an encoding standard for plain text. Copying font identity implies styled text, just like copying italic or bold copying.

javascript's picture

@oldnick: I expressed / proposed clean non-dirty law abiding development without any font piracy.

javascript's picture

?Unicode Consortium: What tends to happen with some development organisations once they become sustainable, they start to ignore practical / usability issues and artificially typecast (sic) themselves. There are some transferable resources they could distribute to these practical / usability issues.

quadibloc's picture

This doesn't directly relate to the topic of this thread, but I happened to be searching for documents on Google Books, and ran across a copy of the New Testament translated into the Multani language.

I had admired an image of that script when I saw it in a book on the history of written language, so I searched for further information.

It turned out that the language, also called Saraiki, Derwal, or Wuch (the last being the name of the province where it was spoken; the first is the name usually used today) was written both with the script I had seen, the Lahnda script (the language was also, incorrectly, assigned to the "Southern Lahnda" language group) and with a variation of the Arabic script.

Hindus used Lahnda, Muslims used the Arabic script. The area where Saraiki is spoken is mostly within Pakistan (part of it is in Afghanistan), and so when India was partitioned, the Hindu speakers of Multani or Saraiki fled to India, in which they are scattered. Many still speak the language, but little is published for them in their script any longer, as they also use the language of the surrounding communities to which they have moved.

As a result, the Lahnda script has declined enough in importance that it is not yet among those encoded in Unicode.

Té Rowan's picture

Rich text or plain text isn't a Unicode Consortium problem, as far as I can see.

@oldnick - Yes, extracting the exact names of the fonts used (which is what I believe @javascript meant) is a huuuge piracy problem.

Ray Larabie's picture

Dammit, I got trolled in the wrong thread again. When will I ever learn?

Té Rowan's picture

'Bout the same time I do: When we cross the Styx for kicks.

Syndicate content Syndicate content