Custom Web Publishing Guide

Appendix C
|
Converting CDML solutions to FileMaker XSLT 123
1 In CDML, field and database name comparisons were case-insensitive, which allowed you to use a tag
such as [FMP-Field:myfield] to refer to a field named MyField or myField. In XSLT-CWP, field and database
name comparisons are case-sensitive if they are not used in a query string. In the converted stylesheets,
you must manually fix any field and database names in XSLT statements (excluding query strings) to
exactly match the names used in the database solution, including the case of the name.
For example, in this statement:
<xsl:value-of select="fmrs:field[@name='LastName']"/>
the field reference LastName must exactly match the name and case of the LastName field in the database.
Note In XSLT-CWP, field and database names used in query strings are case-insensitive. See
“Guidelines for using query commands and parameters” on page 86.
1 In CDML, you could compare fields without including the field attribute. For example, you could use
either [FMP-If: myfield.eq.10] or [FMP-If: field:myfield.eq.10]. In this example, because the field attribute is not
included in the comparison, the CDML Converter converts myfield as a string literal instead of a field
name.
For example, after conversion, this CDML statement:
[FMP-If: myfield.eq.10]
is converted to these XSLT-CWP statements:
<xsl:choose>
<xsl:when test="'myfield' = '10'">Ten</xsl:when>
</xsl:choose>
To fix this type of problem, you must manually fix the statement to have the appropriate field name in
the comparison statements in the converted stylesheet. Alternatively, you can add "field:" to the CDML
file where required and reconvert the file.
1 The CDML Converter fixes several instances of malformed HTML that are generated by Claris Home
Page, assuming that the metatags are included in the beginning of the HTML page. If the metatags have
been removed, the CDML Converter will not fix the malformed HTML. There may be other instances
of malformed HTML in Claris Home Page or other HTML files that the CDML Converter cannot fix and
convert properly to XHTML, which is more strictly constructed than HTML. In cases where malformed
HTML was not converted correctly, you must manually fix the XHTML in the converted stylesheet.
1 The CDML Converter adds a .jpg filename extension to all image filename references when it converts
–img action tags. For example, the CDML Converter converts this request:
/fmpro?–db=products.fp5&–format=format_file.html&–lay=sales&–recid=123&–img
to this XSLT-CWP request:
/fmi/xsl/data.jpg?–db=products&–lay=sales&–recid=123
If the .jpg filename extension is incorrect for your solution, you must manually change the extension in
filename references in the converted stylesheets.
1 The CDML Converter cannot convert nested (embedded) forms. If you nest forms, you need to either
change your CDML solution or fix the resulting .xsl file.