From: Alexandre Krispin <k.m.alexandre@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Error while compiling : ! String contains an invalid utf-8 sequence.
Date: Sat, 26 Nov 2011 00:56:59 +0100 [thread overview]
Message-ID: <CAA5sP+9RR2npxuTcXnW9-kdcJrjFH7wJ1rZxyOvO9xdvut2_-g@mail.gmail.com> (raw)
In-Reply-To: <4ECFF60D.1090804@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 4636 bytes --]
Now that japanese display correctly, there is still another problem.
Japanese sentences (long titles in bibliography) don't break at the end of
line. I have tested the behavior of japanese with entire paragraphs, and I
get the same problem as in the bibliography, lines don't break and go
"through" the page.
Though I have looked to documentation about chinese on the wiki, none
helped me to solve this problem. Does someone have any idea ?
Here is a minimal example with a paragraph sample in japanese :
%%%%%%%%%beginning of file%%%%%%%%%%
\usemodule[simplefonts]
\setmainfont[HeiseiMinStd-W3]
\definesimplefonttypeface[jpn][HeiseiMinStd-W3]
\setupbodyfont[12pt]
\setuptolerance[\v!verytolerant,\v!stretch]
\enableregime[utf]
\usemodule[typearea]
\setupTypeArea[bcor=30mm,alphabets=2.6,oneside]
%*********************************
\starttext
そしてディズニー原理主義で考えた場合、「一秒24コマの絵」で作るフルアニメが至上。そのルールに照らした場合、「電脳コイル」より「らき☆すた(ハルヒ)」の方が優れている。
ニョロニョロと滑らかに動く。つまりそれだけ動画枚数を多く使ってる。よりフルアニメに近い。よって「電脳コイル<らき☆すた」となる。
コレに作画マニアは反論する。アニメは「アニメーターのスキル」こそが最も重要。「スキル>作画枚数」、だから優れたアニメーターである磯光雄の手掛けた電脳コイルのほうが偉い。
じゃあ磯光雄がフルアニメにしたら?今の2コマ3コマ打ちの磯光雄より偉いの?より優れてるの?
>フルアニメの磯光雄の方が優れている。
この場合、「リミテッドアニメという制約の中で独自の進化をした日本アニメのアイデンティティ」というのが無くなってしまう。「らき☆すた」には勝てるがファンタジアには負ける。
>2、3コマ打ちのリミテッドの磯光雄の方が優れている。
質としては等価(磯光雄の原画)でより量のあるフルアニメよりもリミテッドアニメの方が優れてる、その理由を言語化する必要がある。
じゃあ、そのリミテッドで手に入れた価値とは何?
例えば「フルアニメと同じ価値をリミテッド(より少ない動画枚数=コスト)で作れるという『省エネ』の部分にある」ってこと?ソレだと新たな創作的価値を別に産み出してないよね。
そうでないのなら動きの質がディズニーとはどう違うの?
\stoptext
%%%%%%%%%end of file%%%%%%%%%%%%%
I attach the corresponding pdf file I obtain after compilation.
2011/11/25 Hans Hagen <pragma@wxs.nl>
> On 25-11-2011 20:03, Christian wrote:
>
> Same here. It messes up when converting .bib to .bbl. Maybe check your
>> bbl file, too. Mine looks like this, for example:
>> a={{Hirofumi Uzawa~宇沢弘文}}
>>
>> You could try to write the .bbl file directly yourself, although that is
>> not a comfortable option, if you have many Japanese entries.
>> Apart from that there's not much coming to mind.
>>
>
> It makes me wonder how Thomas gets his greek etc done in bibtex.
>
> Hans
>
>
> ------------------------------**------------------------------**-----
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> ------------------------------**------------------------------**-----
>
> ______________________________**______________________________**
> _______________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/**
> listinfo/ntg-context <http://www.ntg.nl/mailman/listinfo/ntg-context>
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/**projects/contextrev/<http://foundry.supelec.fr/projects/contextrev/>
> wiki : http://contextgarden.net
> ______________________________**______________________________**
> _______________________
>
--
------------------------------------------------------------------------------
Alexandre KRISPIN
41 rue Guynemer | 93200 Saint-Denis | France
tél : 06 28 76 69 34 | http://bijutsu.toile-libre.org
----------------------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 6032 bytes --]
[-- Attachment #2: biblio.pdf --]
[-- Type: application/pdf, Size: 42897 bytes --]
[-- Attachment #3: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-11-25 23:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 18:50 Alexandre Krispin
2011-11-25 19:03 ` Christian
2011-11-25 20:09 ` Hans Hagen
2011-11-25 22:13 ` Alexandre Krispin
2011-11-25 23:56 ` Alexandre Krispin [this message]
2011-11-27 13:33 ` Mojca Miklavec
2011-11-27 16:13 ` Alexandre Krispin
2011-11-28 9:20 ` Wolfgang Schuster
2011-12-07 8:28 ` Thomas A. Schmitz
2011-12-07 16:37 ` Alexandre Krispin
2011-12-07 17:45 ` Hans Hagen
2011-11-26 9:35 ` Ulrike Fischer
2011-11-26 10:44 ` Alexandre Krispin
2011-11-26 11:39 ` Wolfgang Schuster
2011-11-26 11:41 ` Alexandre Krispin
[not found] <mailman.901.1322405047.4232.ntg-context@ntg.nl>
2011-11-28 7:08 ` S Barmeier
2011-11-28 8:42 ` Alexandre Krispin
2011-11-30 12:25 ` Alexandre Krispin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA5sP+9RR2npxuTcXnW9-kdcJrjFH7wJ1rZxyOvO9xdvut2_-g@mail.gmail.com \
--to=k.m.alexandre@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).