Projects tagged ‘xhtml’ and ‘xsl’

PHP5 includes an object for handling XML files using DOM; TDOM seeks to simplify the handling of different types of XML-based files, including: SVG, XUL Interfaces, DocBook?, RDF, XML, (x) HTML and ... [More] thanks to its interface via plugins try to incorporate many more (eg RSS, Atom). * Reading XML Files * Writing XML Files * Creation of Files (SVG, Docbook, etc) * Creating XML files from another sources (databases, files, LDAP, etc) * Modification and transformation * Screen output [Less]

Set of extensions to Apache and other Web servers to provide consistent authentication and presentation of various existing 3rd party web applications.

Contributors: iroybot Donate link: http://contactsheet.de/donate.xhtml Tags: wysiwyg, authoring, editor, edit, rich editor, rich text editor, rich formatting, text formatting, css, valid, xhtml, html ... [More] , tiny, replacement, backend, admin panel, admin cp, xml, xsl XStandard Version included: 2.0.0.0 Requires at least: 2.7.1 Tested up to: 2.7.1 Trunk Version: 0.5 Stable Version: -DescriptionIntegrates XStandard Editor into WordPress. XStandard is a standards-compliant, flexible and highly customizable WYSIWYG-solution. It ensures, the that your markup validates against XHTML 1.0 Strict and XHTML 1.1 specifications. Configure your WYSIWYGs on the XStandard Options Page (if you enable this feature, users can customize their WYSIWYG settings in their Profile Page or on a per post basis. By Erik Pöhler. Screenshot News, Info, Updateswill announce stable version here Changelog22/03/2009 - v0.5 added postmeta_field 'edited_with_xstandard' in order not try fixing valid markup. still incomplete alpha. serious browser problems. need more testing. 03/02/2009 - v0.5 mocking up the options page. still an incomplete alpha. 02/24/2009 - v0.5 uploaded new rewrite of the plugin. (yes, from scratch). still an incomplete alpha 02/23/2009 - moved v0.2 to a branch folder - deprecated from wp2.0.x days 02/23/2007 - v0.2 initial release/testing version. seemed to work. TODO and Brainstorminglow priority enhancement: button. for now more stays intact. low priority task: Get your hands on features not yet implemented such as proxy settings, additional HTTP headers normal priority: Intensive testing with random theme stylesheets. low priority: Theming the editor could be a big plus. for example two or three different themes (basically icons, placeholders) normal priority: Make a tutorial on how to use the JS hooks. For example by providing something useful like a microformats plugin-addon, or a more-button. Collect ideas and Feedback from pioneer users. high priority: Make sure the numerous typography plugins like typogrify will still work with XStandard normal priority: manage User and Role specific settings. (I had good experiences with the role manager plugins in the past. However, the downside is that only people with this tool installed are able to fully make use of applying new xstandard privileges to single users, user groups and roles. If I would code a solution for this on my own it would be an hilarious amount of work... high priority: There are many risky scenarios where the inserted content is not what it should be. (verify the encoding. twice. important task.) disabling wpautop makes sense in many ways (performance, making sure valid xhtml doesn't get messed up with all those regex guessing), but what happens with published posts? We need a test here. A flag/meta field or something that tells WordPress if a post has been published with XStandard (thus it IS XHTML and doesn't need that filters that tinkerMCE obviously needs so much) normal priority:Beautify the folder structure. Think this through some more. File based customization (eg. the user xmls or an interface to customize?) low priority: Add Inline Editing feature. (so logged-in users can quickly edit articles on the website) high priority: Bad problem with the folded menu in the admin cp. XStandard behaves like max z-index. Resolvedhigh priority: find out how to save valid xhtml posts in a way, that doesn't make wordpress strip all markup when the plugin is deactivated (and regular post filters apply).(comment: regular post filters should have no problem with valid markup) Run far far away if people report bugs. (comment: no one does. :) pheew. ) [Less]

PhPeace is an open-source CMS (Content Management System), whose primary target are Non-Profit Organisations. Conceived by Carlo Gubitosa and Francesco Iannuzzelli for PeaceLink, an italian ... [More] pacifist association, it has been developed in Php and it's currently available in English and Italian. [Less]

Mark-up Modification Language (MML), otherwise called Mammle. This new language was developed to allow modification of DOM (XML) documents without physically modifying the XML document or having to ... [More] change the structure of the document (XSL). While not specifically designed for Search Engine Optimization professionals (SEO), it makes a perfect choice for individuals who require to make modifications to the HTML code before it is served to the user. What this means is separation of SEO code from actual web development code, allowing developers and SEO individuals to easily work side-by-side without conflicts. Mammle files contain a .mml extension and are executed by an IIS module or Apache module (depending on the server environment) after the page has been rendered. This allows MML to co-exist with any type of server-side language (.NET, ASP, PHP, Java, Ruby, etc) under the Windows or Linux environments. While it is possible to translate an XML-based document using XSL, it is not so straight-forward to simply modify a document without the need to change the structural mark-up. This language makes it simple to modify XML-based documents, without needing to have a strong background in programming and reduces the amount of code required. Mammle makes use of the XQuery/XPath syntax (as in XSL documents) as well as contains some CSS-based properties. [Less]

New ReleaseUpdated documentatin to come. v3.0 includes many bug fixes and enhanced funtionality. Dexter is a tool for producing XSLT 1.0-compliant stylesheets to style arbitrary XML data into ... [More] human-readable XHTML using the design document as the source. Thus changes to the visual layout may be propagated directly to the XSLT through a predictable, automated process. While it can be used with many other XML formats such as WML or RSS, formats with complex attribute-value structures such as SVG will be supported with extension modules in the future. Dexter allows users to define extended attributes which can be associated with descriptors and editors. These attributes can be embedded into any well-formed XML document. The resulting embellished document, the 'source', is then input to the dexter engine. This will generate one or more XSLT stylesheets describing the input document interpolating editor modifications and any instructions specified by the descriptors. Operations are specified exclusively with extended attributes embedded in per-module custom namespaces so web browsers will continue to see the decorated source exactly as the web designer saw it before. Thus, the changes we effect while preparing the design document as source for dexter are effectively transparent to all but dexter. Input Documents Dexter does not validate input documents, but does expect them to be strictly well-formed XML or XHTML as it uses the JVM's default configured JAXP parser to produce the Document object against which dexter performs it's operations. This constraint helps guarantee that the documents produced from the resulting XSLT will accurately reflect the input document. Dexter is designed to handle arbitrarily complex input documents so long as they are well-formed. Example Usage For an example of dexter's usage, refer to dexter.html. It serves as the design document for dexter's documentation and is used to generate dexter.html.xsl which styles the documentation pages. View the source for dexter.html and scan for attributes in the dx and dd namespaces; they have been been extensively commented. To see the resulting stylesheet applied, refer to any of the documents listed on the right under links such as the User Guide For more detailed information about descriptor in the dx namespace refer to User Guide#Dexterity. Operations in the dd namespace are documented under User Guide#Didi. [Less]

This is OpenWiki modification. The goal is to crete classic ASP wiki engine that'll look and feel as Mediawiki. Main differences from OpenWiki: MIME type changed to application/xhtml+xml proper ... [More] MathML rendering by Gecko based browsers out-of-the-box (e.g. Firefox) IE with MathPlayer add-on spam defence by reCAPTCHA support Features in development: support for Mediawiki css (partially implemented) support for Mediawiki client scripts (partially implemented) Sites using this engine: NEQwiki, the nonlinear equations encyclopedia [Less]

The Google Search Appliance Mobile Stylesheet defines a user interface for your Google Search Appliance to enable enterprise search by mobile workers. It customizes the look and behavior of Google's ... [More] search page and search results page for optimal viewing on handheld devices. These devices typically have smaller screens and less memory and computational power than their PC counterparts. RequirementsGoogle Search Appliance running software version 4.6.2.S.22 or later A browser (user agent) capable of parsing and viewing XHTML documents A WAP 2.0 compliant device is required for browsing XHTML Mobile Profile documents New XHTML/Multifunction Stylesheet!The Google Enterprise XHTML/Multifunction Stylesheet also offers Mobile support, plus it is more up-to-date with many additional features. Give it a try today! [Less]

The Google Search Appliance XHTML Stylesheet defines a user interface for your Google Search Appliance that conforms to modern web standards including XHTML 1.0 Strict, XHTML Mobile Profile (XHTML-MP) ... [More] and CSS 2.1. It generates well-formed, valid markup and is accessible in a variety of browsers and presentation modes. RequirementsGoogle Search Appliance running software version 4.6.2.S.22 or later A browser (user agent) capable of parsing and viewing XHTML documents A WAP 2.0 compliant device is required for browsing XHTML Mobile Profile documents New 'Multifunction' Version (Beta)UPDATE 22 May 2008: Concurrent with Google Search Appliance software version 5.0.0.G.14. Compatible with Google Search Appliance and Google Mini. Includes additional support for: Atom 1.0 Google Analytics Google Desktop for Enterprise HTML 4.01 Strict HTML 5 a.k.a. (X)HTML5 OpenSearch 1.1 RSS 2.0 Earlybird adopters, curiosity seekers, et al. are encouraged to tire-kick. Please note - this is NOT the same thing as the Featured Download at the top-right of this page. This is a newer release that has yet to be folded in to a ZIP download with all the trimmings. Learn more, peruse the online documentation (in progress) or download the source and take it for a test-drive right now. (Last Update: 23 May 2008) Find any issues? Have comments or feedback? Write early, write often! [Less]

Our aim with parcl is to create a content management system with very little overhead and taking modularity to a new level with creating everything non-essential to safely and automatically loading ... [More] the modules into modules. To achieve this we use PHP5 and its object oriented programming capabilities for the script itself. The InnoDB storage engine for MySQL to achieve better database integrity through its ACID compliance and XSL Transformations for the template system. AJAX implementation through the jQuery java script library is also planned. Of course will all output be XHTML 1.0 Strict (or XHTML 1.1 if the browser supports it) and CSS2.1 valid, using UTF-8 encoding and there are accessibility implementations on the horizon. [Less]