# CSL processor news

**URL:** <https://discourse.citationstyles.org/t/csl-processor-news/540>\
**Category:** CSL Development\
**Created:** [February 10, 2009, 12:48pm UTC](https://discourse.citationstyles.org/t/csl-processor-news/540 "2009-02-10T12:48:05Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [March 5, 2009, 1:37am UTC](https://discourse.citationstyles.org/t/csl-processor-news/540/21 "2009-03-05T01:37:02Z")

</div>

…

> It’s just a sample, you can write tests for larger blocks of CSL with  
> the same layout. Fine-grained tests like this of individual elements  
> and attributes are helpful to a coder, though, to provide a target for  
> specific functionality, and to identify specific areas of misbehaviour  
> when later changes to a program mess things up.

Right, but the results examples are a) specific to one output format  
(HTML) and b) could be represented many ways in that format and still  
be correct. E.g. rather than …

“_some title_”

… you could have:

“_some title_”

… or:

“some title”

… or:

“some title”

All of them would yield the same display.

So am simply observing it’d be nice to be able to operate a level  
above that if possible to avoid that problem.

Bruce

---

<div class="post-metadata">

**Author:** ![Simon\_Kornblith](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Simon\_Kornblith](https://discourse.citationstyles.org/u/Simon_Kornblith)\
**Post date:** [March 5, 2009, 1:59am UTC](https://discourse.citationstyles.org/t/csl-processor-news/540/22 "2009-03-05T01:59:17Z")

</div>

Do you have any idea what this level would be? It agree that this is a  
real issue (especially if you were to have something like ), but I have no  
inspiration as far as good ways of handling it. The three cases you’ve  
mentioned could all be accommodated by easily with simple string  
replace operations, but the above case would be a little more difficult.

Simon

---

<div class="post-metadata">

**Author:** ![Frank\_Bennett](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/frank_bennett/32/198_2.png) [@Frank\_Bennett](https://discourse.citationstyles.org/u/Frank_Bennett)\
**Post date:** [March 5, 2009, 2:48am UTC](https://discourse.citationstyles.org/t/csl-processor-news/540/23 "2009-03-05T02:48:54Z")

</div>

> …
> 
> It’s just a sample, you can write tests for larger blocks of CSL with
> 
> the same layout. Fine-grained tests like this of individual elements
> 
> and attributes are helpful to a coder, though, to provide a target for
> 
> specific functionality, and to identify specific areas of misbehaviour
> 
> when later changes to a program mess things up.
> 
> Right, but the results examples are a) specific to one output format  
> (HTML) and b) could be represented many ways in that format and still  
> be correct. E.g. rather than …

We’re just trying to confirm that the engine is capable of doing the  
right thing. The markup can be generated by a driver specific to the  
testing process, and it can contain any symbols you like. I used HTML  
just because it’s familiar to me, but if something else should be  
used, no problem.

> “_some title_”
> 
> … you could have:
> 
> “_some title_”
> 
> … or:
> 
> “some title”
> 
> … or:
> 
> “some title”
> 
> All of them would yield the same display.
> 
> So am simply observing it’d be nice to be able to operate a level  
> above that if possible to avoid that problem.
> 
> Do you have any idea what this level would be? It agree that this is a real  
> issue (especially if you were to have something like ), but I have no inspiration as  
> far as good ways of handling it. The three cases you’ve mentioned could all  
> be accommodated by easily with simple string replace operations, but the  
> above case would be a little more difficult.

Can you combine tags like that in RTF? If not, I think you can safely  
assume the harder case away (we might check the existing  
implementations just to be sure no one is getting burned). What would  
be a problem is a markup language that requires formatting hints to be  
combined in this way, and does not permit them to be nested. I can’t  
think of any, but my knowledge is limited.

Frank

---

<div class="post-metadata">

**Author:** ![Frank\_Bennett](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/frank_bennett/32/198_2.png) [@Frank\_Bennett](https://discourse.citationstyles.org/u/Frank_Bennett)\
**Post date:** [March 5, 2009, 3:08am UTC](https://discourse.citationstyles.org/t/csl-processor-news/540/24 "2009-03-05T03:08:04Z")

</div>

> > …
> > 
> > It’s just a sample, you can write tests for larger blocks of CSL with
> > 
> > the same layout. Fine-grained tests like this of individual elements
> > 
> > and attributes are helpful to a coder, though, to provide a target for
> > 
> > specific functionality, and to identify specific areas of misbehaviour
> > 
> > when later changes to a program mess things up.
> > 
> > Right, but the results examples are a) specific to one output format  
> > (HTML) and b) could be represented many ways in that format and still  
> > be correct. E.g. rather than …
> 
> We’re just trying to confirm that the engine is capable of doing the  
> right thing. The markup can be generated by a driver specific to the  
> testing process, and it can contain any symbols you like. I used HTML  
> just because it’s familiar to me, but if something else should be  
> used, no problem.
> 
> > “_some title_”
> > 
> > … you could have:
> > 
> > “_some title_”
> > 
> > … or:
> > 
> > “some title”
> > 
> > … or:
> > 
> > “some title”
> > 
> > All of them would yield the same display.
> > 
> > So am simply observing it’d be nice to be able to operate a level  
> > above that if possible to avoid that problem.
> > 
> > Do you have any idea what this level would be? It agree that this is a real  
> > issue (especially if you were to have something like ), but I have no inspiration as  
> > far as good ways of handling it. The three cases you’ve mentioned could all  
> > be accommodated by easily with simple string replace operations, but the  
> > above case would be a little more difficult.
> 
> Can you combine tags like that in RTF? If not, I think you can safely  
> assume the harder case away (we might check the existing  
> implementations just to be sure no one is getting burned). What would  
> be a problem is a markup language that requires formatting hints to be  
> combined in this way, and does not permit them to be nested. I can’t  
> think of any, but my knowledge is limited.

There might be some engines that don’t control the order of nesting  
for some decorations:

_ **My Title** _  
**_My Title_**

For this, and for Simon’s harder case, I guess alternative valid  
responses could be specified in the JSON by enclosing a set of results  
in an array.

---

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [March 5, 2009, 4:16pm UTC](https://discourse.citationstyles.org/t/csl-processor-news/540/25 "2009-03-05T16:16:38Z")

</div>

…

> There might be some engines that don’t control the order of nesting  
> for some decorations:
> 
> _ **My Title** _  
> **_My Title_**
> 
> For this, and for Simon’s harder case, I guess alternative valid  
> responses could be specified in the JSON by enclosing a set of results  
> in an array.

Yeah.

I guess we just need to ask, what do we need to test for output? For a  
test on styling, can we not just test for only that?

Similarly, we can have tests that only check other specific output things:

- field order
- substitution
- year-suffix generation and other disambiguation
- quote handing
- name display
- punctuation and whitespace

Bruce

---

<div class="post-metadata">

**Author:** ![Frank\_Bennett](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/frank_bennett/32/198_2.png) [@Frank\_Bennett](https://discourse.citationstyles.org/u/Frank_Bennett)\
**Post date:** [March 5, 2009, 10:07pm UTC](https://discourse.citationstyles.org/t/csl-processor-news/540/26 "2009-03-05T22:07:50Z")

</div>

> …
> 
> > There might be some engines that don’t control the order of nesting  
> > for some decorations:
> > 
> > _ **My Title** _  
> > **_My Title_**
> > 
> > For this, and for Simon’s harder case, I guess alternative valid  
> > responses could be specified in the JSON by enclosing a set of results  
> > in an array.
> 
> Yeah.
> 
> I guess we just need to ask, what do we need to test for output? For a  
> test on styling, can we not just test for only that?
> 
> Similarly, we can have tests that only check other specific output things:
> 
> - field order
> - substitution
> - year-suffix generation and other disambiguation
> - quote handing
> - name display
> - punctuation and whitespace

-

---

<div class="post-metadata">

**Author:** ![Frank\_Bennett](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/frank_bennett/32/198_2.png) [@Frank\_Bennett](https://discourse.citationstyles.org/u/Frank_Bennett)\
**Post date:** [March 6, 2009, 3:18am UTC](https://discourse.citationstyles.org/t/csl-processor-news/540/27 "2009-03-06T03:18:48Z")

</div>

> > Hi Frank,  
> > Whose “summer”; the one down south, or up north? So June, or December?
> 
> He teaches in Japan, so the one north… June, I believe.
> 
> Frank, thanks for your contribution, I’m looking forward to seeing you  
> back here hacking again. Its’ been a pleasure getting to know I’m not  
> the only comparative lawyer wasting her time and jeopardizing an  
> academic career just for the joy of coding. 😉

Andrea,

The feeling is mutual, I’ve been very glad to discover your work.  
I’ll be following the list in the next months, I’m just taking a  
holiday from work on the program. This morning I did some final  
tidying up in the code and comments, and the online version gives a  
very clear picture of how things fit together.

The programmers that built the English website of our faculty  
([http://gsl-nagoya-u.net](http://gsl-nagoya-u.net)) are big on Haskell and Ruby. Their main  
line of work is not connected with biblio management in any way, but  
their site is here if you’re interested, with a blog (My Beautiful  
Code) where they occasionally post on software process and design:  
[http://www.starling-software.com/en/](http://www.starling-software.com/en/)

Frank

[Previous page](https://discourse.citationstyles.org/t/csl-processor-news/540.md?page=1)
