Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
Locked
0

Where to find TLF Markup xsd schema?

New Here ,
Sep 02, 2009 Sep 02, 2009

Anybody knows?

TOPICS
Text layout framework
1.8K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 02, 2009 Sep 02, 2009

Nope.  We haven't written one.

The general issue of describing the markup needs to be addressed.   I have some content I can reformat and post as a blog entry - its descriptive.  I'll look into doing that.

Richard

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 03, 2009 Sep 03, 2009

Well, my idea was to embed flow:TextFlow to another xsd schema which describes some features not supported by Markup syntax such as bulleted/numbered lists and tables.

So could you please make a notification when you decide to formalize Markup syntax into xsd?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 11, 2010 May 11, 2010

I am also working on an extended mapping for XHTML => TextFlow. Would be nice to have a decent specification (XSD) which could be used to validate the resulting TextFlow tree. Any news on that issue?  My idea is to transform XHTML to TextFlow markup (XML objects) in order to be able to address on the missing extended XHTML support of the TLF (due to its HTML facilities being a subset of Flash MX 2004 TextArea component's HTML).

And it should be validatable, because HTML markup is not TextFlow markup and there might be differences which can break the stuff you want to display and therefore such differences will need to be addressed using some kind of validation technology!

The only thing I would like to achieve is a straightforward solution for that problem by providing the TLF framework with standards-based XML content. The result should be extendable, but not too complex at first. And it should just work. That means it would suffice, if bad markup nodes could be ignored at first, while concentrating on a decent text display with the use of standards-based CSS (inline-) stylesheet information (which also needs to be mapped to TextFlow style attributes and properties)...

Any help or thoughts are welcome!

Best regards,
Manuel Fittko

P.S.:

I have just found an interesting source for creating the mapping which could then be used to build the TextFlow markup from XHTML data. Prove me wrong!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 11, 2010 May 11, 2010
LATEST

See also the FXG spec, found here: http://opensource.adobe.com/wiki/display/flexsdk/FXG+2.0+Specification. If you look at the section entitled "FXG Text", a RichText element has a <content> child, and a <content> is a TextFlow. That is, the contents of a <content> element are all the same as the contents of a TextFlow. The attributes that might otherwise appear on the TextFlow, appear on the RichText element.

I hope this is enough to get you started! If your project allows it, please post your schema back here -- I'm certain you aren't the only one with interest.

Thanks,

- robin

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines