Re: latex bibliographies with multiple databases

Gidday gidday

As for entering unicode via jedit, there is a graphical plugin for it:
http://plugins.jedit.org/plugins/?CharacterMap
But I haven't been able to get it to work with unicode and it seems that 
the current implementation is a tad broken:
http://community.jedit.org/?q=node/view/1628&pollresults%5B1252%5D=1
We have to wait for a fix to be uploaded.

The good thing about using unicode as storage is that it's a blank slate 
and that means that if the community decides that some kind of markup is 
in fact useful the maintainer(s!) can choose to support it at a later 
point via whatever method they like and in theory they(he!) know(s) 
exactly what kind of data is in the database at any given time: i.e. 
more control over what is coming in and out. See I wouldn't be surprised 
if the required-capitalisation markup was asked for at some time in the 
future when a user wants to use latex+docbook but exploit the latex 
markup, but it can be done from a unicode starting point anyway. My 8.2 
cents worth

Incidentally, how do docbook users deal with this capitalisation issue? 
i.e. capitalisation of acronyms and proper nouns versus of subtitles and 
improper nouns. Anyone?

Peace
Damien

David Nebauer wrote:
> Damien Jade Duff wrote:
> 
>>>all-caps, and mixed case output.
>>>    
>>
>>The latter is fine except, as before, when your article title 
>>capitalises verbs and improper nouns. I'm happy to do it this way 
>>though, I'll just make sure no capitalised verbs and improper nouns get 
>>into my database and hope not to encounter citation styles that require 
>>them.
> 
> 
> This has been bothering me. If the default model for encoding is:
> 
> ...........XML......LaTeX
> ............|.........|
> ............|.........|
> INPUT.....unicode.unicode
> .............\......./
> ..............\...../
> ...............\.../
> ................\./
> .................v
> STORAGE.......unicode
> ................/.\
> .............../...\
> ............../.....\
> ............./.......\
> OUTPUT....convert.convert
> ............|.........|
> ............|.........|
> ............v.........v
> 
> There will undoubtedly be users like Damien who make the choice to 
> include markup in their bibliographic data. Although it effectively 
> traps them into one output format the trade-off is greater control over 
> how that data is eventually displayed.
> 
> Would not it be simple, given the above model, to have a command line 
> switch for runbib and refdbib that skips the conversion step? That seems 
> to me an easy way to accommodate the wishes of everybody.
> 
> Regards,
> David.
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Refdb-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/refdb-devel


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642