Re: multlingual titles in refdb
"O'Donnell, Dan" <[email protected]> Tue, 12 Jan 2010 08:13:46 -0700
| Newsgroups | gmane.text.refdb.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============8143989255415120552== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA939A.6DFC5781" This is a multi-part message in MIME format. ------_=_NextPart_001_01CA939A.6DFC5781 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Given how unsupported this is at the moment regardless of software, I = wonder if a kluge might not be the way to go no matter what system you = use, Christian? I.e. code the data with a wiki-style token that you = could later use to extract a xml:lang attribute from. e.g. +fr+Les temps = perdus; +en+Remembrance of things past It might be much easier to build the language tokens into an existing = bibliographic database than to build a bibliographic database from the = ground up. How does MARC handle this?=20 Daniel Paul O'Donnell, PhD Associate Professor, Department of English, University of Lethbridge Lethbridge AB T1K 3M4 Canada Chair, Text Encoding Initiative (http://www.tei-c.org/) Director, Digital Medievalist Project = (http://www.digitalmedievalist.org/) -----Original Message----- From: Christian Wittern [mailto:[email protected]] Sent: Tue 2010-01-12 5:14 To: [email protected] Subject: Re: [Refdb-users] multlingual titles in refdb =20 Dear Markus, Thanks for your answer. What a pity, RefDB would otherwise quiet nicely = fit the bill. Unfortunately, I am not aware of other software that=20 could do this. MODS maybe could be shoehorned to support this, but last = time I checked it did not have xml:lang in the schema. TEI could do=20 this, so I might have to go with a custom made XML database (eXist) or=20 some such:-( All the best, Christian On 2010-01-12 19:15, Markus Hoenicka wrote: > Christian Wittern<[email protected]> was heard to say: > > =20 >> Hi there, >> >> For a project here, I would like to adopt refdb for bibliographic = data >> management. However, one of the requirements is to be able to have >> multilingual titles, that is titles repeated for different languages. = As an >> example, I might have a title of a Japanese paper in original script >> (Kanji+Kana), Roman Transcription, translation into English, = translation >> into German etc. >> I wonder how refdb could deal with this. It appears that at the = moment all >> fields are language-agnostic, right? Would it be possible to = introduce >> language at some level? >> =20 > Hi, > > RefDB cannot deal with this at the moment. Current practice in > biomedical sciences is to provide the native title, followed by the > translated title in square brackets. I'm well aware that this is not > sufficient for the humanities. > > Adding language support to article and publication titles requires a > couple of internal changes. Currently the title is part of the main > reference entry, except for periodical titles which are already stored > in a separate table. At this time RefDB only supports a fixed number > of periodical synonyms. In order to support titles in different > languages, we'd have to change this to a key-value kind of storage, > with multiple keys indicating the type and language of a title. This > is basically doable, but it will require quite a bit of coding time > (which I'm particularly short of at the moment). Also, it will require > extensions to the query language as you'd have to be able to query > specific translations of a title to make full use of these changes, > something like ":TX[en]:~whatever" to query the English version of a > title. Adding language support to other fields (which ones would be > required?) would follow the same pattern and would add quite a bit of > complexity to the whole thing. > > To sum it up, RefDB could be modified to suit your needs, but this is > nothing that I could do on a rainy sunday afternoon. > > regards, > Markus > > > > > > =20 --=20 Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN -------------------------------------------------------------------------= ----- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and = easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev=20 _______________________________________________ Refdb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/refdb-users ------_=_NextPart_001_01CA939A.6DFC5781 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7654.12"> <TITLE>RE: [Refdb-users] multlingual titles in refdb</TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <P><FONT SIZE=3D2>Given how unsupported this is at the moment regardless = of software, I wonder if a kluge might not be the way to go no matter = what system you use, Christian? I.e. code the data with a wiki-style = token that you could later use to extract a xml:lang attribute from. = e.g. +fr+Les temps perdus; +en+Remembrance of things past<BR> <BR> It might be much easier to build the language tokens into an existing = bibliographic database than to build a bibliographic database from the = ground up. How does MARC handle this?<BR> <BR> Daniel Paul O'Donnell, PhD<BR> Associate Professor,<BR> Department of English,<BR> University of Lethbridge<BR> Lethbridge AB T1K 3M4<BR> Canada<BR> <BR> Chair, Text Encoding Initiative (<A = HREF=3D"http://www.tei-c.org/">http://www.tei-c.org/</A>)<BR> Director, Digital Medievalist Project (<A = HREF=3D"http://www.digitalmedievalist.org/">http://www.digitalmedievalist= .org/</A>)<BR> <BR> <BR> <BR> -----Original Message-----<BR> From: Christian Wittern [<A = HREF=3D"mailto:[email protected]">mailto:[email protected]</A>]<BR> Sent: Tue 2010-01-12 5:14<BR> To: [email protected]<BR> Subject: Re: [Refdb-users] multlingual titles in refdb<BR> <BR> Dear Markus,<BR> <BR> Thanks for your answer. What a pity, RefDB would otherwise quiet = nicely<BR> fit the bill. Unfortunately, I am not aware of other software = that<BR> could do this. MODS maybe could be shoehorned to support this, but = last<BR> time I checked it did not have xml:lang in the schema. TEI could = do<BR> this, so I might have to go with a custom made XML database (eXist) = or<BR> some such:-(<BR> <BR> All the best,<BR> <BR> Christian<BR> <BR> On 2010-01-12 19:15, Markus Hoenicka wrote:<BR> > Christian Wittern<[email protected]> was heard to = say:<BR> ><BR> > <BR> >> Hi there,<BR> >><BR> >> For a project here, I would like to adopt refdb for = bibliographic data<BR> >> management. However, one of the requirements is to be = able to have<BR> >> multilingual titles, that is titles repeated for different = languages. As an<BR> >> example, I might have a title of a Japanese paper in original = script<BR> >> (Kanji+Kana), Roman Transcription, translation into English, = translation<BR> >> into German etc.<BR> >> I wonder how refdb could deal with this. It appears that = at the moment all<BR> >> fields are language-agnostic, right? Would it be possible = to introduce<BR> >> language at some level?<BR> >> <BR> > Hi,<BR> ><BR> > RefDB cannot deal with this at the moment. Current practice in<BR> > biomedical sciences is to provide the native title, followed by = the<BR> > translated title in square brackets. I'm well aware that this is = not<BR> > sufficient for the humanities.<BR> ><BR> > Adding language support to article and publication titles requires = a<BR> > couple of internal changes. Currently the title is part of the = main<BR> > reference entry, except for periodical titles which are already = stored<BR> > in a separate table. At this time RefDB only supports a fixed = number<BR> > of periodical synonyms. In order to support titles in different<BR> > languages, we'd have to change this to a key-value kind of = storage,<BR> > with multiple keys indicating the type and language of a title. = This<BR> > is basically doable, but it will require quite a bit of coding = time<BR> > (which I'm particularly short of at the moment). Also, it will = require<BR> > extensions to the query language as you'd have to be able to = query<BR> > specific translations of a title to make full use of these = changes,<BR> > something like ":TX[en]:~whatever" to query the English = version of a<BR> > title. Adding language support to other fields (which ones would = be<BR> > required?) would follow the same pattern and would add quite a bit = of<BR> > complexity to the whole thing.<BR> ><BR> > To sum it up, RefDB could be modified to suit your needs, but this = is<BR> > nothing that I could do on a rainy sunday afternoon.<BR> ><BR> > regards,<BR> > Markus<BR> ><BR> ><BR> ><BR> ><BR> ><BR> > <BR> <BR> <BR> --<BR> Christian Wittern<BR> Institute for Research in Humanities, Kyoto University<BR> 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, = JAPAN<BR> <BR> <BR> -------------------------------------------------------------------------= -----<BR> This SF.Net email is sponsored by the Verizon Developer Community<BR> Take advantage of Verizon's best-in-class app development support<BR> A streamlined, 14 day to market process makes app distribution fast and = easy<BR> Join now and get one step closer to millions of Verizon customers<BR> <A = HREF=3D"http://p.sf.net/sfu/verizon-dev2dev">http://p.sf.net/sfu/verizon-= dev2dev</A><BR> _______________________________________________<BR> Refdb-users mailing list<BR> [email protected]<BR> <A = HREF=3D"https://lists.sourceforge.net/lists/listinfo/refdb-users">https:/= /lists.sourceforge.net/lists/listinfo/refdb-users</A><BR> <BR> </FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01CA939A.6DFC5781-- --===============8143989255415120552== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev --===============8143989255415120552== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Refdb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/refdb-users --===============8143989255415120552==--