ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Starting with bibliography / international entries
Date: Mon, 13 Oct 2014 21:18:39 +0600	[thread overview]
Message-ID: <147F0280-151C-4B3A-B528-964BDBCABDAD@fiee.net> (raw)
In-Reply-To: <F46CC469-4EE9-4BFE-9BCD-C7050E9CB327@fiee.net>

Am 2014-10-13 um 18:00 schrieb Henning Hraban Ramm <texml@fiee.net>:

> Am 2014-10-13 um 16:49 schrieb Wolfgang Schuster <schuster.wolfgang@gmail.com>:
> 
>> The context suite comes with the file mkiv-publications.pdf which is the manual for the new bibliography mechanism.
> 
> Thanks for the hint, I didn’t look after that.
> 
> I guess I will use the Lua syntax, since it’s the shortest.

… or stay with .bib, since there are tools for it, and maybe someone else might need my data.

> And hopefully I’ll figure out how to setup the output ;-)
> 
> But how would you cope with the international (i.e. Cyrillic) titles/authors?
> Should I define fields like author_original or is there a better way (maybe define the book twice, using crossref)?

I found this about BibLaTeX / Babel:
http://tex.stackexchange.com/questions/28010/how-to-create-multilingual-english-japanese-bibliographies-with-biblatex-bib
It’s nearly the same problem as mine.

BibLaTeX 3.0 + Biber 2.0 are advertised to support this syntax:

@COLLECTION{yanagida_zengaku_sosho_1975,
  LANGID = {japanese},
  EDITOR = {柳田聖山},
  EDITOR_romanised = {Yanagida, Seizan},
  TITLE = {禪學叢書},
  TITLE_romanised = {Chūbun shuppansha},
  TITLE_translated_english = {Collected Materials for the Study of Zen},
  LOCATION = {京都},
  LOCATION_romanised = {Kyōto},
  LOCATION_translated_english = {Kyoto},
  PUBLISHER = {中文出版社},
  PUBLISHER_romanised = {Chūbun shuppansha},
  DATE = {1974/1977}
}

… and extract the right version according to configuration.
Is there support for these constructed keys in ConTeXt?

Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2014-10-13 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 10:31 Henning Hraban Ramm
2014-10-13 10:49 ` Wolfgang Schuster
2014-10-13 12:00   ` Henning Hraban Ramm
2014-10-13 15:18     ` Henning Hraban Ramm [this message]
2014-10-13 16:22       ` Hans Hagen
2014-10-14  8:19         ` Ulrike Fischer
2014-10-14  9:41           ` Hans Hagen
2014-10-14 12:06             ` Ulrike Fischer
2014-10-15 14:21               ` Alan BRASLAU

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=147F0280-151C-4B3A-B528-964BDBCABDAD@fiee.net \
    --to=texml@fiee.net \
    --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).