From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: t-bib cannot do with Chinese.
Date: Wed, 11 Mar 2009 09:31:58 +0100 [thread overview]
Message-ID: <49B776FE.9020300@wxs.nl> (raw)
In-Reply-To: <49B7775D.10708@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030"; Format="flowed", Size: 2657 bytes --]
Wei-Wei Guo wrote:
> Dear all,
>
> My .tex and .bib files are at the end of the email. The commands I run are
>
> context bibtry && context bibtry
>
> The first `context bibtry` is ok but no .bbl file generated. The second one
> complains
>
> publications : loading database from bibtry.bbl
> (bibtry.bbl
> ! Text line contains an invalid utf-8 sequence.
> l.22 n=2,s=
> 0202020286]
>
> Can t-bib do with Chinese bib entry? or is it just a problem of bibtex?
>
> I'm using MkIV(current trunk) and t-bib(march 2, 2009).
>
>
> BTW. Is only absolute path can be used in \setupbibtex?
>
>
> Thanks.
>
> Best wishes,
> Wei-Wei Guo
>
>
> ============ bibtry.tex ===========
>
> \usemodule[bib]
>
> \setupbibtex[database=~/mytry.bib]
>
> \starttext
>
> English Bibliogrphy \cite[article-full].
>
> ÖÐÎÄÎÄÏ× \cite[c-article-full] ¡£
>
> \completepublications
>
> \stoptext
>
> ==================================
>
>
> ============= mytry.bib ==========
>
> @ARTICLE{article-full,
> author = {L[eslie] A. Aamport and L[eslie] A. Aamport and L[eslie] A.
> Aamport and L[eslie] A. Aamport},
> title = {The Gnats and Gnus Document Preparation System},
> journal = {\mbox{G-Animal's} Journal},
> year = 1986,
> volume = 41,
> number = 7,
> pages = "73--83",
> month = jul,
> note = "This is a full ARTICLE entry",
> }
>
> @ARTICLE{c-article-full,
> author = {ÐÕÃûÒ» and ÐÕÃû¶þ and ÐÕÃûÈý and ÐÕÃûËÄ},
> title = {ÎÄÕÂÌâÄ¿},
> journal = {ijijÔÓÖ¾¶þ},
> year = 1986,
> volume = 41,
> number = 7,
> pages = "73--82",
> month = jul,
> note = "This is a full ARTICLE entry",
> language = "chinese"
> }
you might want to look into mlbibtex then (it supports context)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-11 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 8:33 Wei-Wei Guo
2009-03-11 8:31 ` Hans Hagen [this message]
2009-03-11 9:17 ` Wei-Wei Guo
2009-03-11 8:33 ` Taco Hoekwater
2009-03-11 9:14 ` Wei-Wei Guo
2009-03-11 9:26 ` Taco Hoekwater
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=49B776FE.9020300@wxs.nl \
--to=pragma@wxs.nl \
--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).