Re: [Unicode] Re: Fonts and font sizes used in the Unicode

2018-03-05 Thread Asmus Freytag via Unicode

  
  
On 3/5/2018 9:03 AM, suzuki toshiya via
  Unicode wrote:

I
  have a question; if some people try to make a
  
  translated version of Unicode, they should contact
  
  all font contributors and ask for the license?
  
  Unicode Consortium cannot give any sublicense?

Be happy to help you get an answer to that
off-list,
in case you are actually working on a translation 
project. The issue is too specific and complex to
give general answers.
A./
  
  



Re: [Unicode] Re: Fonts and font sizes used in the Unicode

2018-03-05 Thread Markus Scherer via Unicode
On Mon, Mar 5, 2018 at 9:03 AM, suzuki toshiya via Unicode <
unicode@unicode.org> wrote:

> I have a question; if some people try to make a
> translated version of Unicode, they should contact
> all font contributors and ask for the license?
> Unicode Consortium cannot give any sublicense?
>

If you want to translate the Unicode Standard or its companion standards
(UAX, UTS, ...), then please contact the Unicode Consortium.

Thus, I guess, it would not be so irrelevant to ask
> the permission to JTC1, about the fonts used in
> ISO/IEC 10646 - although it does not mean that
> JTC1 would permit anything. If I'm misunderstanding,
> please correct me.
>

The production of the ISO 10646 standard is done by the Unicode Consortium.
I am fuzzy on what exactly that means for copyright. If you need to find
out, then please contact the consortium.

markus


Re: [Unicode] Re: Fonts and font sizes used in the Unicode

2018-03-05 Thread suzuki toshiya via Unicode

Hi,

I remember, the front page of the code charts by
Unicode has following note:


Fonts
The shapes of the reference glyphs used in these code
charts are not prescriptive. Considerable variation is
to be expected in actual fonts. The particular fonts
used in these charts were provided to the Unicode
Consortium by a number of different font designers,
who own the rights to the fonts.

See http://www.unicode.org/charts/fonts.html for a list.


--

I have a question; if some people try to make a
translated version of Unicode, they should contact
all font contributors and ask for the license?
Unicode Consortium cannot give any sublicense?

If I understand correctly, ISO/IEC JTC1 hold the
copyright of the materials used in the published
documents of JTC1 standard, because they have to
permit the production of the translated version of
their standards, the reuse of the content of a spec
by another spec, etc.

Thus, I guess, it would not be so irrelevant to ask
the permission to JTC1, about the fonts used in
ISO/IEC 10646 - although it does not mean that
JTC1 would permit anything. If I'm misunderstanding,
please correct me.

Regards,
mpsuzuki

On 3/5/2018 4:49 AM, Asmus Freytag via Unicode wrote:

On 3/4/2018 9:12 AM, Markus Scherer via Unicode wrote:
On Sun, Mar 4, 2018 at 6:10 AM, Helena Miton via Unicode 
> wrote:
Greetings. Is there a way to know which font and font size have been used in 
the Unicode charts (for various writing systems)? Many thanks!

What are you trying to do?

Many of the fonts are unique to the Unicode chart production, and are not 
licensed for other uses. Some are not even generally usable.

markus

The editors of the Unicode charts will use any font resource that gets the job 
done (that is, results in a chart that correctly displays the characters in the 
standard). These fonts are often not production fonts, and may lack any of the 
many tables needed to actually display running text. They may also, as has been 
mentioned, be licensed solely for the purpose of publishing the standard. In 
some cases, they are custom built.

For most scripts, the font size is nominally set to 22pt in the main code 
charts, but the tool that the editors use allow a different size to be selected 
for any range of code points, or individual characters. There are some examples 
where a character is very wide or tall where it had to be scaled down 
individually to fit the cell.

The purpose of the code charts is *exclusively* that of helping users of the 
standard identify which character is encoded at what code position. They are 
not intended as a font resource or normative description of the glyphs. Any 
usage scenario that is outside the very narrow scope is unsupported and reverse 
engineering / extracting font resources is explicitly in violation of the terms 
of use.

A./