Re: Licence for XSL-FO schema
Licence for XSL-FO schema Jeremias Maerki <[EMAIL PROTECTED]> Date: Tue, 25 Feb 2003 16:57:33 +0100 Is it safe to believe that we can add the Apache licence to the XSL-FO schema from Chuck Paussa? Or does he also have to do an explicit copyright transfer, first? Please add an Apache license to the XSL-FO schema that I developed. There are no other legal encumbrances on that document. Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP compliance in XML?
Benoit, In the FOP schema I developed, there's a set of switches that you have to edit in order to differentiate between what is and is not supported in FOP. The schema, as I provided it, validates for the full FO spec. You need to go in and comment out the templates with a name of ???_NOT in order to exclude those elements that are not supported. There are also individual comments on some elements and values as to whether specific values are supported. For instance, check in the schema for "Inherit" In most cases, the spec says that it is a valid value and yet FOP rejects it as invalid and then inherits anyway. Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP schema
Victor Mote and Peter West wrote: > I noticed from your commt that the 'country-name's had lost their > spaces, e.g., MACEDONIA,THEFORMERYUGOSLAVREPUBLICOF. > . . . > However, the 3-letter language codes are the ones we need. I took the text for that section from one of the ISO standards. I wasn't sure which standard I should be applying. The text in there should track with the valid values for those fields. The country name text isn't actually used in the schema but, It is very useful for populating drop-down lists etc. in any interface generated from the schema. >> While working on an FAQ for FO dtd & schema, I see that we have two schema in docs/foschema: fop4f.xsd & fop4.xsd. > I then did similar clanups on fop4g.xsd, and committed that as a change to fop4.xsd. (etc.) > See > http://marc.theaimsgroup.com/?l=fop-dev&m=103547432006815&w=4 > If no one objects, I would like to move this information to fop.xsd & let > CVS handle the revision issues. The viewcvs program allows us to append a > revision number, so we could even branch & tag this to keep it tied to > releases. > Victor Mote Guys, I created the FOP schema for me and posted it to the list so everyone else could benefit from my work. Feel free to change it however you like. I put some stuff in there in the sections so I could generate automated tests, I segregated the FOP implemented and non-implemented features etc. Someone else posted that they'd like to put in some schematron extensions. That would be cool too. Chuck > Chuck, if you want me to post a copy of the file to you, let me know. Yes, please cross post the changes to me since I'm not hooked up to the CVS. Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: fo validation issue (Latest FO schema)
Oleg and Peter, Here's the latest iteration of the fo schema. Could someone commit it? The only change is to allow % in length attributes. I believe that the schematron folks are working on a schematron validator that works as an extension to the schema (By adding schematron extensions to the element.) I cetainly can't work on anything of that magnitude for a while (months+) since this one catches all of the mistakes that my team is likely to make. If anyone wants to take on the task of extending the schema with schematron asserts. Feel free. Chuck Paussa > Hello! > I've been thinking about fop users most confused questions and then about general > solution for detection input tree related errors and finally I arrived at the old idea > (raised already on the list) of input tree validation. > Why not? It's quite simple to create schematron schema for xsl-fo, define > understandable asserts, then compile it into xsl stylesheet (or even into java class using > xalan's xsltc) during fop building and use it as optional sax filter at run-rime. fop4g.zip Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Area Tree attributes
While looking for a solution to a theoretical problem, I've recently had reason to look at the area tree generated with the -at command line switch. I notice that it is filled with these constructs: And, I'm thinking to myself . . . "Oh. Wouldn't it be nice if I could set that name in my fo document and have it show up in the area tree." 1. Is there a way to set that name from the FO document? Note: Area container uses names like footnote-reference-area, after, before, before-float-reference-area, main-reference-area, etc. Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Latest version (f) of FO Schema
Here's the latest version. I've better organized the comments and cleaned up some things. I haven't coded for the possibility of including functions in attribute values. Which functions has FOP implemented? Also, Can I assume that the following is true? 1. All functions that return object can be applied anywhere. 2. Numeric functions apply to length, integer, and number values. 3. Color functions apply to color values. 4. from-table-column applies to table-cell and any element that can be a child of a table-cell. 5. proportional-column-width applies only to table-column Functions: numericfloor( numeric) numericceiling(numeric) numericround(numeric) numericmin( numeric , numeric) numericmax(numeric , numeric) numericabs( numeric) colorrgb(numeric , numeric , numeric) colorrgb-icc(numeric , numeric , numeric , NCName , numeric , numeric) colorsystem-color( NCName) objectsystem-font( NCName , NCName) objectinherited-property-value(NCName) numericlabel-end() numericbody-start() objectfrom-parent( NCName) objectfrom-nearest-specified-value( NCName) objectfrom-table-column( NCName) numericproportional-column-width( numeric) objectmerge-property-values( NCName) The spec also specifies this attribute, which applies to the page context (So which elements signify the page context?) Chuck Paussa fop4f.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Latest FO Schema Improved
OK, done in my copy. I'll post it again next week Chuck Oleg Tkachenko wrote: > Hello! > > Another problem: border-width doesn't understand "1px" value, my > proposal is to extend border_margin_width_Type to allow non negative > length values: > > > > > > > > > > > > > > > > > Where non-negative-length_Type is defined as > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Latest FO Schema Improved
Oleg, Oleg Tkachenko wrote: > P.S. I believe full-fledged fo schema would be a very useful thing. Would you mind if I contribute to this project? You just did contribute. Thanks. I'll include your change (and any others anyone sends me) in the next draft. I'll post it next week to give other people time to respond. I've got nothing in my own FO documents that even come close to exercising the full spec. If we want to develop a full-fledged and validated schema, I'll need contributions from people who have a real need to validate complex documents. Chuck Oleg Tkachenko wrote: > Hello! > > Chuck Paussa wrote: > I've improved the FO schema adding much better type patterns and adding a bunch of attributes that I'd missed the first time around. > > Well done! I tried to validate my fo documents and the first validation error I got was about content - I have some meta info there in my namespace. Spec says: > --- > Contents: > (color-profile)+ > > The fo:declarations flow object may have additional child elements in a non-XSL namespace. Their presence > does not, however, change the semantics of the XSL namespace objects and properties. The permitted > structure of these non-XSL namespace elements is defined for their namespace(s). > > > So, I suppose, schema declaration for the element should be as follows: > > > > > > > > > > > > btw, this declaration assumes that all elements must come before other stuff, which is not required by spec, but I cannot see any way to express such constraints in schema, one could use instead of , but this way we lose control over (color-profile)+ constraint. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Latest FO Schema Improved
I've improved the FO schema adding much better type patterns and adding a bunch of attributes that I'd missed the first time around. Chuck Paussa fop4e.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Latest FOP schema
Kieron wrote: > This looks very good. > I think we should put this somewhere on the site when it is ready. That would be excellent Not quite done yet. I missed the attributes in the spec that are only listed as applying to elements but are not referred to in the element description. I'm confused bt the description of some of these attributes. "background-position" applies to block-level and replaced elements (What are replaced elements?) "max-width""min-height""min-width" apply to all elements except non-replaced inline elements and table elements (What are non-replaced inline elements?) "position" applies to all elements, but not to generated content (What is generated content?) The following attributes are listed in the spec as applying to all elements. (This makes sense) "background" "border-bottom" "border-color" "border-left" "border-right" "border-style" "border-top" "border-width" "margin" "page-break-after" "page-break-before" apply to block-level elements, list-item, and table-row (This makes sense) Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Latest FOP schema
I've greatly improved the FO schema I've been working on. I've added patterns for most of the attribute types. I'd appreciate it if some folks would run their FO documents through a validator against this schema and respond with where I've done a less than excellent job. The schema as delivered is for the full FO spec. I've created s and s that segregate those elements and attributes implemented and not-implemented in FOP. To make this an FOP only schema, remove those groups and attributeGroups with "_Not" in their names. A couple of items I've noticed: FOP allows some elements, like fo:table-cell and fo:flow to be empty when the spec says they must be non-empty FOP allows the contents of some elements like simple-page-master to be in any order when the spec insists on a defined order Chuck Paussa fop4e.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: What the spec says about table-row, table-cell etc.
OK, so I ran the following XPATH on the spec //div3[(@id = ./head/quote) and (.//table/tbody/tr[./td = 'Inherited: ']/td[(position() = 2) and (text() = 'yes')])]/head/quote And got the following universally inheritable attributes which I will add into my schema font-familyletter-spacing font-selection-strategytext-transform font-stretch word-spacing font-size-adjust color font-style intrusion-displace font-variant keep-together font-weightorphans countrywidows language leader-alignment script leader-pattern hyphenate leader-pattern-width hyphenation-character leader-length hyphenation-push-character-count rule-style hyphenation-remain-character-count rule-thickness start-indent auto-restore end-indent border-collapse display-align border-separation relative-align caption-side hyphenation-keep empty-cells hyphenation-ladder-count direction last-line-end-indent glyph-orientation-horizontal line-heightglyph-orientation-vertical line-height-shift-adjustment provisional-label-separation line-stacking-strategy provisional-distance-between-starts linefeed-treatment score-spaces white-space-treatment visibility text-align border-spacing text-align-lastfont text-indentpage-break-inside white-space-collapse white-space wrap-optionxml:lang Arved wrote: Comments below. >>>> -Original Message- >>>> From: Chuck Paussa [mailto:[EMAIL PROTECTED]] >>>> Sent: May 2, 2002 7:16 PM >>>> To: [EMAIL PROTECTED] >>>> Subject: What the spec says about table-row, table-cell etc. >>>> >>>> >>>> I've been working on a schema for FO documents so that I can off-load >>>> the validation chore. I created the schema from the W3C documents which >>>> state the following for table-cell: >>>> >>>> Contents: >>>> >>>> (%block;)+ >>>> >>>> In addition this formatting object may have a sequence of zero or more >>>> fo:markers as its initial children. >>>> >>>> The following properties apply to this formatting object: >>>> >>>> * [7.4 Common Accessibility Properties] >>>> * [7.6 Common Aural Properties] >>>> * [7.7 Common Border, Padding, and Background Properties] >>>> * [7.12 Common Relative Position Properties] >>>> * [7.26.1 "border-after-precedence"] >>>> * [7.26.2 "border-before-precedence"] >>>> * [7.26.4 "border-end-precedence"] >>>> * [7.26.6 "border-start-precedence"] >>>> * [7.14.1 "block-progression-dimension"] >>>> * [7.26.8 "column-number"] >>>> * [7.13.4 "display-align"] >>>> * [7.13.6 "relative-align"] >>>> * [7.26.10 "empty-cells"] >>>> * [7.26.11 "ends-row"] >>>> * [7.14.4 "height"] >>>> * [7.28.2 "id"] >>>> * [7.14.5 "inline-progression-dimension"] >>>> * [7.26.13 "number-columns-spanned"] >>>> * [7.26.14 "number-rows-spanned"] >>>> * [7.26.15 "starts-row"] >>>> * [7.14.12 "width"] >>>> >>>> FOP, in addition, both allows and implements the setting of block's >>>> inheritable attributes such as "color" and "text-align" which are then >>>> propagated down to the enclosed blocks. My questions are as follows: >>>> >>>> Is there a place in the spec that says "Containers may hold inheritable >>>> attributes so they can be passed on to their child objects"? >>>> Or is this just a side-effect of inheritabliity? >>>> Or is this illegal and will disappear in future FOP versions to be >>>> compatible with the spec? >> >> >> > > Yes, at Section 5.1.4. Every inheritable property exists on every formatting object, whether or not the property is actually applicable to (useable by) that FO. This isn't just a side-efefct of inheritability, this _is_ inheritability. :-) >>>> and >>>> >>>> Is there a list of these "inheritable attributes" ? Or do I just >>>> generate the list from those attributes that have an enumeration value >>>> of inherit? >> >> >> > > Don't do the latter...what you want to want to look at is the "Inherited:" field in the property descriptions. Chuck, one thing you may find helpful (maybe you've done it already) is to work off the XML version of the spec, and extract the property tables, at which point you can do SAX or XSLT to get at interesting bits. This was my approach. Regards, Arved
FOP has not implemented defined enumerated attribute values
I wrote a test document that implemented all of the enumerated values for block attributes. Here are the results where FOP complained. All of the other enumerated values seem to be implemented. For the value "inherit" FOP implements inheritability. It just doesn't recognize the inherit enumerated value. font-weight bolder = unknown font lighter = unknown font inherit = unknown font font-style backslant = unknown font inherit = unknown font position inherit = Unknown enumerated value breaks inherit = Unknown enumerated value hyphenate inherit = Unknown enumerated value white-space-collapse inherit = Unknown enumerated value wrap-option inherit = Unknown enumerated value span inherit = Unknown enumerated value border-style inherit = Unknown enumerated value text-decoration inherit = Unknown enumerated value text-align-last inside = Unknown enumerated value outside = Unknown enumerated value left= Unknown enumerated value right = Unknown enumerated value inherit = Unknown enumerated value text-align inside = Unknown enumerated value outside = Unknown enumerated value inherit = Unknown enumerated value color inherit = unknown colour name dominant-baseline property is not implemented yet white-space-treatment property ignored linefeed-treatmentproperty is not implemented yet alignment-baselineproperty is not implemented yet alignment-adjust property is not implemented yet Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
What the spec says about table-row, table-cell etc.
I've been working on a schema for FO documents so that I can off-load the validation chore. I created the schema from the W3C documents which state the following for table-cell: Contents: (%block;)+ In addition this formatting object may have a sequence of zero or more fo:markers as its initial children. The following properties apply to this formatting object: * [7.4 Common Accessibility Properties] * [7.6 Common Aural Properties] * [7.7 Common Border, Padding, and Background Properties] * [7.12 Common Relative Position Properties] * [7.26.1 "border-after-precedence"] * [7.26.2 "border-before-precedence"] * [7.26.4 "border-end-precedence"] * [7.26.6 "border-start-precedence"] * [7.14.1 "block-progression-dimension"] * [7.26.8 "column-number"] * [7.13.4 "display-align"] * [7.13.6 "relative-align"] * [7.26.10 "empty-cells"] * [7.26.11 "ends-row"] * [7.14.4 "height"] * [7.28.2 "id"] * [7.14.5 "inline-progression-dimension"] * [7.26.13 "number-columns-spanned"] * [7.26.14 "number-rows-spanned"] * [7.26.15 "starts-row"] * [7.14.12 "width"] FOP, in addition, both allows and implements the setting of block's inheritable attributes such as "color" and "text-align" which are then propagated down to the enclosed blocks. My questions are as follows: Is there a place in the spec that says "Containers may hold inheritable attributes so they can be passed on to their child objects"? Or is this just a side-effect of inheritabliity? Or is this illegal and will disappear in future FOP versions to be compatible with the spec? and Is there a list of these "inheritable attributes" ? Or do I just generate the list from those attributes that have an enumeration value of inherit? Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP DTD attached (updated)
David, If you look at the comments at the top of the DTD, you'll find instructions on how to strip out those elements not implemented in FOP Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FOP Schema
I've generated and cleaned up the attached schema from the XSL FO DTD. These are fairly clean documents with some additions like enumerated types for lengths and percentages. The enumerated types do not exclude values not implemenetd in FOP. One item to note is that the element names in the schema do not include the fo: prefix, so if you're generating code from the schema, you'll have to work around that. Post any comments and I'll include them in the next update. [Even the cranky comments I've gotten so far are useful];-) Chuck Paussa fop_xsd.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FOP DTD attached (updated)
DTD lovers I've created the attached DTD from the XSL FO W3C documents. I updated the DTD to allow you to exclude those elements that are not handled by FOP. These are fairly clean documents with some additions like enumerated types for lengths and percentages. The enumerated types do not exclude values not implemenetd in FOP. The DTD should work well with PSGML. Post any comments and I'll include them in the next update. [Even the cranky comments I've gotten so far are useful];-) Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Example extension
Matt, I've written the following sample fo document that puts in continued on following pages. Unfortunately fo:retrieve-marker does not work within the so it cannot be implemented in the but instead in a table palced in the region-before. This is not a problem if you are starting a new page sequence for pages that will not have table elements that need a header. Also, you can use this open-source product for watermarks http://www.etymon.com/pj/index.html Chuck Paussa Matt Savino wrote > I've been told than an extension is the way to go for these two needed > features: > > 1. Add a string ['(Continued)'] to a table header if the table spans > multiple pages. Note these tables are part of the content and > can start > anywhere in the page. They could be seen more like paragraphs > or blocks > with a title. Any other solution to this problem is acceptable. > > 2. Separate page number display for a subsection. IE - master document > is page 4 of 7, but subsection is page 2 of 3. > > Please let me know if I'm missing any existing functionality > that solves > these problems. I am planning to look into writing an extension some > day. An example would certainly help. > http://www.w3.org/1999/XSL/Format";> Project AC/Series Blah Blah Blah Blah ContinuedBlah Blah Blah Blah ContinuedBlah Blah Blah Blah ContinuedBlah Blah Blah Blah ContinuedBlah Blah Blah Blah ContinuedBlah Blah Blah Blah ContinuedBlah Blah Blah Blah - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP0.20.3
Markers are broken in Fop-0.20.3rc2 the presence of an fo:marker tag --> error I don't know if this should be entered as a bug since markers were not completely implemented previously [INFO]: FOP 0.20.3rc [INFO]: building formatting object tree [ERROR]: null Here is the sample test.fo http://www.w3.org/1999/XSL/Format";> One this is a test this is a test this is a test this is a test this is a test this is a test this is a test this is a test Chuck Paussa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Is there a XML-Schema of XSL:FO?
Christian I was the person who posted the FO DTD. I haven't posted the XSD (XML-Schema) because I haven't tested the DTD yet. You've got XML Spy, just take the DTD and run it through the conversion. "DTD/Schema" - "Convert DTD/Schema" - Check "W3C Schema", "Elements", and "Make Global Definition". I want to keep it in the DTD form during testing for two reasons 1. The recommendation is in DTD format so I can cut and paste a lot of stuff 2. The DTD format allows me to define substitution variables for "attributes supported by FOP" / "Not supported by FOP" so I can easily generate an FOP specific XSD vs. a validating XSD The XSD is cool because I can write XSLs to generate text editor macro code and FO test cases and stuff like that. The downside of the DTD format is that I haven't found a utility that will convert the DTD substitution variables to XSD defined types. So, after I create the XSD, I have to manually generate the defined types and that's a pain. So . . . I don't want to do it until I've tested the DTD. If anyone wants me to post the XML Spy generated XML-Schema, I will. Chuck __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
fop dtd attached
A couple of people have written in recently asking for an FOP dtd. I'm guessing so they can use it with PSGML. So, I made one using the standard document as well as I could read it. I tried to include lists of valid values for things like so, if you want to use it as a real validating document, those lists are going to invalidate valid integers. (Replace the list with CDATA and you should be fine) Also, the DTD omits the FO: prefix for the elements. Feel free to fix the problems and repost the DTD. FOP DTD attached Chuck __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Dictionary / phone book page formatting
Hi, Some guy asked how to do a dictionary type page with first and last entries on the top-left and top-right of the page. So, I've attached an example of how. There are some ugly bits in this that I need cleared up before I can give you a clean example. Questions, because I'm confused. 1. is an fo:block type container which acts as if it is not contained in its containing block. When I render this, the only way I can position the retrieve-marker is in another table cell. Is this how it is supposed to act? Can I tell it to inherit some property so that it will act like text instead of a block? I noticed that it will display even if it is not contained in a block. This is different from the behavior exhibited by fo:page-number. 2. Notice on page 2. first-including-carryover = Ele even though it is the block named Ten whose carryover is the first on the page 3. On Page 3, the before-region doesn't render, even the static text is gone. I'm guessing because there are no blocks fitting any of the retrieve-marker conditions. I'm also confused by the message [WARN]: Some static content could not fit in the area. on page 3. I'm using FOP-0.20.2 Chuck __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com http://www.w3.org/1999/XSL/Format";> first-starting-within-page: first-including-carryover : last-starting-within-page : last-ending-within-page : One Onea One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One Onez Two Twoa Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Twoz Thr Thra Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thrz Fou Foua Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fouz Fiv Fiva Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fivz Six Sixa Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Sixz Sev Seva Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sevz Eig Eiga Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eig Eigz Nin Nina Nin Nin Nin Nin Nin Nin Ni
