-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Apr 8, 2011, at 1:17 AM, Bruce D'Arcus wrote: > On Thu, Apr 7, 2011 at 4:55 PM, Sylvester Keil <[email protected]> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> On Apr 7, 2011, at 10:18 PM, Bruce D'Arcus wrote: >> >>> On Thu, Apr 7, 2011 at 4:03 PM, Sylvester Keil <[email protected]> wrote: >>> >>>> By the way, (and because I still owe Bruce and Rintze an example) I have >>>> been playing around with converting the citeproc-test JSON data into >>>> cucumber features; you can take a look at an example at: >>>> >>>> https://github.com/inukshuk/citeproc-ruby/blob/master/features/condition/is_numeric.feature >>>> >>>> The advantage of cucumber features is that they are extremely intuitive >>>> and easy to write. Although, in this case the main complexity in >>>> formulating a test case is in defining the style and input data. >>> >>> Yes. Only downside is it's then Ruby-specific. >> >> Yes (although I believe there is a Java implementation around); however, the >> step definitions in this case are extremely simple (e.g., see >> https://github.com/inukshuk/citeproc-ruby/blob/master/features/step_definitions/citeproc_steps.rb), >> therefore, you could easily use Ruby sorto of like a shell script that >> fires up rhino, hugs, or ghc and feeds the test data to citeproc-js or >> citeproc-hs. >> >> Not to stray too far off topic, though, you are of course right that an >> implementation agnostic test suite isthe best option going forward. >> >>> Seems you have some other news of sorts: that one can now do "gem >>> install citeproc-ruby". >>> >>> Cool! >> >> It is still very experimental and incomplete but I guess 'release early' >> won't hurt at this point. (It only works in Ruby 1.9. at the moment, though, >> because of differences in unicode handling.) > > I remembered 1.8 didn't deal with unicode very well. But even with > 1.9.2, I get this: > >> x = ['ö','o','a','x'] > => ["ö", "o", "a", "x"] >> x.sort > => ["a", "o", "x", "ö"] > > I was used this just working in saxon. Is there any way to get it to > sort right in 1.9.2? Unicode-Strings are a big mess right now; encoding works like a charm but manipulation is painful; for example this does not work either: x.map(&:upcase) => ["ö", "O", "A", "X"] For this reason I'm currently using the unicode-utils gem (which doesn't support sorting yet I believe), but it is something that I need to assess separately. I remember that Unicode strings worked fairly well under 1.8 using active-support. >> I have also reconsidered your advice and changed the license to a two-clause >> BSD license. > > Still compatible with GPL? Yes. It's the 'FreeBSD' License and it is listed as GPL compatible: http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses Sylvester -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) iEYEARECAAYFAk2e1CQACgkQh4kzvOqyWhAErQCgupjjAIFpJUS/wM+Ch1+q2pzH /TQAoLZo+HCJC1pNQfVHKdu7mEX01U6S =JYLC -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
