Jump to content
Server Maintenance This Week. ×

Basic xsl


John Calder2

This topic is 4970 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

Hi

new to all this and posted same info on the (wrong_ post. Can anyone help:

Hi

I am designing a database which weill export a list of companies to be exported via XML as a web page.

I have the following code at the top of the xsl sheet for my record export:

xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

version="1.0"

xmlns:fmp="http://www.filemaker.com/fmpxmlresult"

exclude-result-prefixes="fmp">

method="html"

encoding="UTF-8"

version="1.0"

omit-xml-declaration="no"

media-type="text/html"

doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"

doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"

indent="yes"/>

The annoying thing is I get the following result at the header part of n my web page:

S4 Work Experience

The meta (META) tag is badly formed - its all upper case and I keep getting error messsages in BBEdit - is this a filemaker problem? or is it me? I know it might be trivial but is there any way I can get this to format in lower case only?

Thanks

Link to comment
Share on other sites

Please do not double-post:

http://fmforums.com/forum/showtopic.php?tid/216775/

If you haven't received a reply, bump the existing thread.

AFAICT, this is a problem with the Xalan-C processor that Filemaker is using to do the transform. I believe you could solve this by changing the output method to xml (or even text) and writing the meta element yourself.

Link to comment
Share on other sites

This topic is 4970 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.