/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ /* * This file is part of the LibreOffice project. * * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. * * This file incorporates work covered by the following license notice: * * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed * with this work for additional information regarding copyright * ownership. The ASF licenses this file to you under the Apache * License, Version 2.0 (the "License"); you may not use this file * except in compliance with the License. You may obtain a copy of * the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
using com::sun::star::uno::XComponentContext; using com::sun::star::uno::Reference; using com::sun::star::uno::Sequence; using com::sun::star::uno::UNO_QUERY; using com::sun::star::uno::UNO_QUERY_THROW; using com::sun::star::xml::dom::DocumentBuilder; using com::sun::star::xml::dom::XDocument; using com::sun::star::xml::dom::XDocumentBuilder; using com::sun::star::xml::dom::XNode; using com::sun::star::xml::dom::XElement; using com::sun::star::xml::dom::NodeType_ELEMENT_NODE;
// TODO: I assume adjacent text nodes should be joined, to preserve // processing model? (I.e., if the SAX parser breaks a string into 2 // Characters(..) calls, the DOM model would still see only one child.)
// create text node and append to parent
Reference<XNode> xNew(
mxNode->getOwnerDocument()->createTextNode( rCharacters ),
UNO_QUERY_THROW );
mxNode->appendChild( xNew );
}
// helper function implementations
static Reference<XNode> lcl_createDomInstance()
{ const Reference<XComponentContext>& xContext = comphelper::getProcessComponentContext();
SAL_WARN_IF( !xContext.is(), "xmloff", "can't get service factory" );
// TODO: come up with proper way of handling namespaces; re-creating the // namespace from the key is NOT a good idea, and will not work for // multiple prefixes for the same namespace. Fortunately, those are rare.
Reference<XElement> xElement;
sal_uInt16 nNamespace = (nElement >> NMSP_SHIFT) - 1; const OUString aPrefix = SvXMLImport::getNamespacePrefixFromToken(nElement, &rImport.GetNamespaceMap()); const OUString& rLocalName = SvXMLImport::getNameFromToken( nElement ); switch( nNamespace )
{ case XML_NAMESPACE_NONE: // no namespace: use local name
xElement = xDocument->createElement( rLocalName ); break; case XML_NAMESPACE_XMLNS: case XML_NAMESPACE_UNKNOWN: // both cases are illegal; raise warning (and use only local name)
xElement = xDocument->createElement( rLocalName );
{
Sequence<OUString> aSeq { rLocalName };
rImport.SetError(
XMLERROR_FLAG_WARNING | XMLERROR_NAMESPACE_TROUBLE, aSeq );
} break; default: // We are only given the prefix and the local name; thus we have to ask // the namespace map to create a qualified name for us. Technically, // this is a bug, since this will fail for multiple prefixes used for // the same namespace.
OUString namespaceURI = SvXMLImport::getNamespaceURIFromToken(nElement);
OUString qualifiedName = aPrefix.isEmpty() ? rLocalName : aPrefix + SvXMLImport::aNamespaceSeparator + rLocalName;
xElement = xDocument->createElementNS(namespaceURI, qualifiedName); break;
}
SAL_WARN_IF( !xElement.is(), "xmloff", "can't create element" );
// add new element to parent and return
xParent->appendChild( xElement ); return xElement;
}
// TODO: come up with proper way of handling namespaces; re-creating the // namespace from the key is NOT a good idea, and will not work for // multiple prefixes for the same namespace. Fortunately, those are rare.
Reference<XElement> xElement; if (rNamespace.isEmpty())
{ // no namespace: use local name
xElement = xDocument->createElement( rName );
} else
{
xElement = xDocument->createElementNS(rNamespace, rName);
}
// add new element to parent and return
xParent->appendChild( xElement ); return xElement;
}
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.