From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Starting with bibliography / international entries
Date: Tue, 14 Oct 2014 11:41:19 +0200 [thread overview]
Message-ID: <543CEFBF.7080307@wxs.nl> (raw)
In-Reply-To: <pcsppnc64960.dlg@nililand.de>
On 10/14/2014 10:19 AM, Ulrike Fischer wrote:
> Am Mon, 13 Oct 2014 18:22:09 +0200 schrieb Hans Hagen:
>
>>> 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:
>
> Well actually (after a renumbering) one needs biblatex 4.0 and biber
> 3.0.
>
>>>
>>> @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?
>>
>> sure, you can use any field you like and you can adapt yoru rendering
>> setups to use them
>>
>> the problem is not so much to support variants of fields (although I
>> really dislike this mixed upper/lowercase mess)
>
> You can write everything in lowercase if you want. The syntax only
> expects the _ to separate the main field and the variant/language.
>
>> the main question is: how mixed is this used? are EDITOR and
>> EDITOR_whatever used at the same time?
>
> You can. There are commands to choose a specific variant, but you
> can also define fallbacks. So something like
> "Editor (Editor_translated)" or "Editor translated but fall back to
> editor if it doesn't exist" is possible.
>
> The main problem is not to get lost in the variants/fallback chains.
That was my initial impression too. There are simply too many
combination possible. In such a case it makes more sense to tune the
rendering than to figure out all the options. So, in context speak that
would mean something:
\btxdoif {title} {
\btxspace
\btxflush{title}
\btxdoifelse {title_variant_b} {
\btxleftparenthesis
\btxflush{title_variant_b}
\btxrightparenthesis
} {
\btxdoif {title_variant_a} {
\btxleftparenthesis
\btxflush{title_variant_a}
\btxrightparenthesis
}
}
\btxperiod
}
Authors are of course somewhat more complex as there one needs to deal
with the way names are constructed. But even then, in such cases
adapting a few setups is not most work.
> Another problem is to get name lists right: After all it is possible
> that only some authors needs to be romanised. But with the help of
> the name hashes I was at the end able to do something like "Müller
> and 柳田聖山 (Yanagida, Seizan) ..."
so basically you order by a mix of name and romanized name (or romanized
name with name as fallback)?
> Smaller problems are how to write the names correctly -- after all
> not everywhere in the world names follows the "lastname, fistname"
> convention.
yes, although if you use APA it might have rules for that (but that is
Alan's speciality)
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
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:[~2014-10-14 9:41 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
2014-10-13 16:22 ` Hans Hagen
2014-10-14 8:19 ` Ulrike Fischer
2014-10-14 9:41 ` Hans Hagen [this message]
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=543CEFBF.7080307@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).