Frank Bennett <[email protected]> writes:
> On Wed, Feb 22, 2012 at 12:15 AM, Charles Parnot
> <[email protected]> wrote:
>> Ah, OK, sorry, I misunderstood as well :-) It's still unclear to me what you 
>> have in mind. Could you give an example of what the CSL would look like?
>>
>> charles
>
> As a first step, I'm just thinking of the easy case, where a DOI or
> URL is rendered in the citation output. One could just apply links
> automatically by default, with a processor toggle to turn links off if
> they are not desired. There wouldn't be any impact on CSL.
>
> I'll be looking at HTML output first, just because I know the markup
> for anchors there. Once I've gotten the processor to provide the
> markup in HTML, it should be simple enough for someone who knows RTF
> syntax to add a similar extension there.
>
> Adding links to arbitrary portions of the output (like the title, as
> Bruce suggests) would be a next step, dependent on extensions to CSL.

A possible solution for the first simple step would be to inspect the
DOI variable:

   - if prefixed by "doi:" I could produce:
     <a href="http://dx.doi.org/10.1038/171737a0";>10.1038/171737a0</a>

   - if prefixed by "http://dx.doi.org/"; I could produce:
     <a 
href="http://dx.doi.org/10.1038/171737a0";>http://dx.doi.org/10.1038/171737a0</a>

   - if not prefixed by I could produce plain text.

Would that make sense?

A new cs:link element I believe should be the possible next step. In
this case affixes could be included in the rendered (linked) element. If
we use a link attribute for the cs:text element, affixes should instead
be excluded from the linked text, right?

Andrea

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

Reply via email to