ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wei-Wei Guo <wwguocn@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use my own BibTeX style (bst)?
Date: Fri, 13 Mar 2009 00:38:56 +0800	[thread overview]
Message-ID: <49B93AA0.1010200@gmail.com> (raw)
In-Reply-To: <49B5363D.4060700@elvenkind.com>

Thank you, Mojca and Taco. I finally get my t-bib working. Now I can
continue working on my bibl style.

Taco Hoekwater 写道:
>> I don't know those styles get adapted automatically when language is
>> changed. Taco should answer (I should take a closer look, but no time
>> now).
> 
> They do not. You have to give a setup command like
> 
>   \setuppublications[alternative=my-zh] % for bibl-my-zh.tex
> 
>> I'm not sure if you can use different style for different books based
>> on language the book was written in (maybe possible, but tedious, the
>> style would have to be rewritten completely).
> 
> With a suitable \setuppublicationlayout this should be possible:
> you can decide based on the value of the current language, which is
> set from the bibtex language field automatically. But I have never
> actually tried to do this, so I have no example code available for you.
> 

I'm still confused. Is it possible to use different bibl based on the value
of \lang. Or I can only implement it with bunch of \if in *one* bibl file?

Best wishes,
Wei-Wei
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2009-03-12 16:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 17:22 Wei-Wei Guo
     [not found] ` <436429714.24327@zju.edu.cn>
     [not found]   ` <49B2ACE1.5010800@gmail.com>
     [not found]     ` <6faad9f00903090800v44877263te205e056cb28d282@mail.gmail.com>
     [not found]       ` <49B5363D.4060700@elvenkind.com>
2009-03-12 16:38         ` Wei-Wei Guo [this message]
2009-03-12 18:29           ` Taco Hoekwater
2009-03-13  1:15             ` Wei-Wei Guo
2009-03-13  8:09               ` Taco Hoekwater
2009-03-13 10:27                 ` Wei-Wei Guo
2009-03-13 17:30                   ` Taco Hoekwater
2009-03-14  4:23                     ` Wei-Wei Guo
2009-03-14  4:32                     ` What does "\c!" means? Wei-Wei Guo
2009-03-14  7:22                       ` Alan Stone
2009-03-14  7:25                         ` Taco Hoekwater
2009-03-14 14:44                           ` Wei-Wei Guo
2009-03-15 15:15                           ` Wei-Wei Guo
2009-03-15 15:38                             ` Wolfgang Schuster
2009-03-15 16:01                             ` Hans Hagen
2009-03-16  5:13                               ` Wei-Wei Guo

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=49B93AA0.1010200@gmail.com \
    --to=wwguocn@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).