[uf-dev] $PRODID$ normalization [was: hCard test 30...]

[brian suda]

Any application that is using the Test Suite will have different PRODIDs
and different SOURCE values. So in the test suites we used $PRODID$
which is replaced by the string in the /bin/test-xlstproc.pl so you can
customize it for your applications output.

We are DIFF'ing the output from xsltproc (or other applications) to the
.vcf files. If someone uses their own application it will have a
different string for the value of PRODID, so instead of hard-coding a
valued in the .vcf files and then during DIFF throwing errors, we used a
variable $PRODID$ which is swapped out so the diff doesn't fail.

does that make more sense? maybe we are talking about two different
things? I'll be around on IRC <abbr title="2006-06-21">today</abbr> that
might clear-up any confusion faster.

-brian

Dan Connolly wrote:
> On Wed, 2006-06-21 at 10:07 -0500, brian suda wrote:
>   
>> Dan Connolly wrote:
>>     
>>> Ryan, you explained how the $SOURCE$ and $PRODID$ normalization
>>> stuff works, but it has since leaked out of my tiny brain.
>>> Would you please explain again?
>>>       
>> Sorry Dan, the  $SOURCE$ and $PRODID$ breaking is my fault.
>>     
>
> Is it? If I know how this stuff is supposed to work, perhaps
> that would be clear to me. But so far, it's not.
>
>   
>>  I have an
>> internal XSLT that i have versioned 0.8 (it is not quite ready to check
>> back in yet). Since the x2v repos and the tests repos are different i
>> up'ed the version number in the tests so my local code passed the tests.
>> Then i checked the tests back in with the newer version number, but not
>> the x2v yet.
>>
>> in /bin/test-xlstproc.pl you can set the $PRODID$ string and the
>> $SOURCE$ strings to match what ever you'd like.
>>     
>
> It's still not clear to me why test-xlstproc.pl should need to
> know the version number from x2v.
>
>   
>> hopefully, if i can find some free time i can finish cleaning-up the
>> XSLT and check that back in too (there have just been a few "issues"
>> lately such as white-space and @headers that need some clean-up).
>>
>> -brian
>>     
>
>