[jira] [Assigned] (XERCESC-2025) Empty line generated when fgDOMXMLDeclaration is disabled
[
https://issues.apache.org/jira/browse/XERCESC-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Cantor reassigned XERCESC-2025:
-
Assignee: (was: Scott Cantor)
> Empty line generated when fgDOMXMLDeclaration is disabled
> -
>
> Key: XERCESC-2025
> URL: https://issues.apache.org/jira/browse/XERCESC-2025
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
>Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4
>Reporter: Jose M. Sanchez
>Priority: Minor
> Labels: DOMLSSerializer, empty, line
>
> The DOMLSSerializer implementation is generating a leading empty line
> in case that the generation of the XML Declaration is disabled.
> The source code looks like this:
> https://svn.apache.org/repos/asf/xerces/c/trunk/src/xercesc/dom/impl/DOMLSSerializerImpl.cpp
> if (getFeature(XML_DECLARATION)) {
> // use the version and encoding resolved
> *fFormatter << gXMLDecl_VersionInfo << fDocumentVersion <<
> gXMLDecl_separator;
> *fFormatter << gXMLDecl_EncodingDecl << fEncodingUsed <<
> gXMLDecl_separator;
> const XMLCh* st = (docu->getXmlStandalone())?
> XMLUni::fgYesString : XMLUni::fgNoString;
> *fFormatter << gXMLDecl_SDDecl << st << gXMLDecl_separator;
> *fFormatter << gXMLDecl_endtag;
> }
> DOMNodeSPtr child = nodeToWrite->getFirstChild();
> while( child != 0)
> {
> processNode(child, level);
> child = child->getNextSibling();
> }
> printNewLine();
> The printNewLine() method is called even if no XML declaration was written,
> thus generating a leading empty line.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Updated] (XERCESC-2025) Empty line generated when fgDOMXMLDeclaration is disabled
[
https://issues.apache.org/jira/browse/XERCESC-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Cantor updated XERCESC-2025:
--
Affects Version/s: 3.0.0
3.0.1
3.1.0
3.1.1
3.1.2
3.1.3
3.1.4
> Empty line generated when fgDOMXMLDeclaration is disabled
> -
>
> Key: XERCESC-2025
> URL: https://issues.apache.org/jira/browse/XERCESC-2025
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
>Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4
>Reporter: Jose M. Sanchez
>Priority: Minor
> Labels: DOMLSSerializer, empty, line
>
> The DOMLSSerializer implementation is generating a leading empty line
> in case that the generation of the XML Declaration is disabled.
> The source code looks like this:
> https://svn.apache.org/repos/asf/xerces/c/trunk/src/xercesc/dom/impl/DOMLSSerializerImpl.cpp
> if (getFeature(XML_DECLARATION)) {
> // use the version and encoding resolved
> *fFormatter << gXMLDecl_VersionInfo << fDocumentVersion <<
> gXMLDecl_separator;
> *fFormatter << gXMLDecl_EncodingDecl << fEncodingUsed <<
> gXMLDecl_separator;
> const XMLCh* st = (docu->getXmlStandalone())?
> XMLUni::fgYesString : XMLUni::fgNoString;
> *fFormatter << gXMLDecl_SDDecl << st << gXMLDecl_separator;
> *fFormatter << gXMLDecl_endtag;
> }
> DOMNodeSPtr child = nodeToWrite->getFirstChild();
> while( child != 0)
> {
> processNode(child, level);
> child = child->getNextSibling();
> }
> printNewLine();
> The printNewLine() method is called even if no XML declaration was written,
> thus generating a leading empty line.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Commented] (XERCESC-2025) Empty line generated when fgDOMXMLDeclaration is disabled
[
https://issues.apache.org/jira/browse/XERCESC-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081416#comment-16081416
]
Scott Cantor commented on XERCESC-2025:
---
The source of the problem isn't the code in the bug report, but the extra
printNewline() calls in each of the Element, Comment, and PI branches of the
processNode method.
The problem is that it would take a redesign to fix it because the
Element/Comment/PI doesn't know what came before it. They might need to print
the LF, and they might not. Fixing it trivially doesn't help, it just moves the
bug to other combinations of content.
> Empty line generated when fgDOMXMLDeclaration is disabled
> -
>
> Key: XERCESC-2025
> URL: https://issues.apache.org/jira/browse/XERCESC-2025
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
>Affects Versions: 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4
>Reporter: Jose M. Sanchez
>Priority: Minor
> Labels: DOMLSSerializer, empty, line
>
> The DOMLSSerializer implementation is generating a leading empty line
> in case that the generation of the XML Declaration is disabled.
> The source code looks like this:
> https://svn.apache.org/repos/asf/xerces/c/trunk/src/xercesc/dom/impl/DOMLSSerializerImpl.cpp
> if (getFeature(XML_DECLARATION)) {
> // use the version and encoding resolved
> *fFormatter << gXMLDecl_VersionInfo << fDocumentVersion <<
> gXMLDecl_separator;
> *fFormatter << gXMLDecl_EncodingDecl << fEncodingUsed <<
> gXMLDecl_separator;
> const XMLCh* st = (docu->getXmlStandalone())?
> XMLUni::fgYesString : XMLUni::fgNoString;
> *fFormatter << gXMLDecl_SDDecl << st << gXMLDecl_separator;
> *fFormatter << gXMLDecl_endtag;
> }
> DOMNodeSPtr child = nodeToWrite->getFirstChild();
> while( child != 0)
> {
> processNode(child, level);
> child = child->getNextSibling();
> }
> printNewLine();
> The printNewLine() method is called even if no XML declaration was written,
> thus generating a leading empty line.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Resolved] (XERCESC-1932) Using xerces-c_3_1D.dll with files compiled under VS-C++ 9.0 on computer which has VS-c++ 6.0 with libraries of VS-c++9.0
[ https://issues.apache.org/jira/browse/XERCESC-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor resolved XERCESC-1932. --- Resolution: Invalid There are no Windows binaries for any current release, so any issue with a build is entirely your own. > Using xerces-c_3_1D.dll with files compiled under VS-C++ 9.0 on computer > which has VS-c++ 6.0 with libraries of VS-c++9.0 > - > > Key: XERCESC-1932 > URL: https://issues.apache.org/jira/browse/XERCESC-1932 > Project: Xerces-C++ > Issue Type: Bug > Components: Miscellaneous >Affects Versions: 3.1.0 > Environment: Microsoft windows XP professional version 2002 SP2, with > VS-C++ 6.0 installed >Reporter: michael n > Attachments: dllload1.exe, dllload.cpp, dllload.exe, msvcp90.dll, > msvcr90.dll, vcredist_x86.exe, xerces-c_3_0D.dll, xerces-c_3_1D.dll, xer > err.JPG > > > The software was compiled on computer with same operating system but with > VS-C++ 9.0 (2008) installed. > When trying to use the program on a platform with same operating system , but > with VS-c++ 6.0 installed (with xerces-c_3_1D.dll ). > I got the Error: > "(1) Error number 126. search in MSDN Help under "Platform SDK (Windows Basic > Services)" subset, topic "System Errors - Numerical Order". > I guessed its cause is the lack of libraries from VS-c++9.0, so I installed > vcredist_x86.exe from Microsoft site, but of no use. > I Would appreciate your help, > Michael -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Closed] (XERCESC-1739) Base64 codec adds LF at the end of last line
[ https://issues.apache.org/jira/browse/XERCESC-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor closed XERCESC-1739. - > Base64 codec adds LF at the end of last line > > > Key: XERCESC-1739 > URL: https://issues.apache.org/jira/browse/XERCESC-1739 > Project: Xerces-C++ > Issue Type: Bug > Components: Utilities >Affects Versions: 1.6.0, 1.7.0, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0, > 2.6.0, 2.7.0 >Reporter: Vladimir Polegenko >Priority: Minor > > According to RFC2045: > The encoded output stream must be represented in lines of no more than 76 > characters each. All line breaks or other characters not found in Base64 > Alphabet must be ignored by decoding software. In base64 data, characters > other than those in Base64 Alphabet, line breaks, and other white space > probably indicate a transmission error, about which a warning message or even > a message rejection might be appropriate under some circumstances. > Therefore, there is no need to add LF at the end of last line. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Reopened] (XERCESC-2025) Empty line generated when fgDOMXMLDeclaration is disabled
[
https://issues.apache.org/jira/browse/XERCESC-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Cantor reopened XERCESC-2025:
---
The other bug filed on this notes that it only occurs when pretty printing is
on, which I didn't test. Will review again.
> Empty line generated when fgDOMXMLDeclaration is disabled
> -
>
> Key: XERCESC-2025
> URL: https://issues.apache.org/jira/browse/XERCESC-2025
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
>Reporter: Jose M. Sanchez
>Assignee: Scott Cantor
>Priority: Minor
> Labels: DOMLSSerializer, empty, line
>
> The DOMLSSerializer implementation is generating a leading empty line
> in case that the generation of the XML Declaration is disabled.
> The source code looks like this:
> https://svn.apache.org/repos/asf/xerces/c/trunk/src/xercesc/dom/impl/DOMLSSerializerImpl.cpp
> if (getFeature(XML_DECLARATION)) {
> // use the version and encoding resolved
> *fFormatter << gXMLDecl_VersionInfo << fDocumentVersion <<
> gXMLDecl_separator;
> *fFormatter << gXMLDecl_EncodingDecl << fEncodingUsed <<
> gXMLDecl_separator;
> const XMLCh* st = (docu->getXmlStandalone())?
> XMLUni::fgYesString : XMLUni::fgNoString;
> *fFormatter << gXMLDecl_SDDecl << st << gXMLDecl_separator;
> *fFormatter << gXMLDecl_endtag;
> }
> DOMNodeSPtr child = nodeToWrite->getFirstChild();
> while( child != 0)
> {
> processNode(child, level);
> child = child->getNextSibling();
> }
> printNewLine();
> The printNewLine() method is called even if no XML declaration was written,
> thus generating a leading empty line.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Assigned] (XERCESC-1902) Stray newline if pretty-printing without xml declaration
[ https://issues.apache.org/jira/browse/XERCESC-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor reassigned XERCESC-1902: - Assignee: Scott Cantor > Stray newline if pretty-printing without xml declaration > > > Key: XERCESC-1902 > URL: https://issues.apache.org/jira/browse/XERCESC-1902 > Project: Xerces-C++ > Issue Type: Bug > Components: DOM >Affects Versions: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4 >Reporter: Boris Kolpackov >Assignee: Scott Cantor >Priority: Minor > Fix For: 3.2.0 > > > If we disable writing xml declaration and enable pretty printing, we get a > stray newline at the beginning of the document: > ' > > ... > > ' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Updated] (XERCESC-1902) Stray newline if pretty-printing without xml declaration
[ https://issues.apache.org/jira/browse/XERCESC-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor updated XERCESC-1902: -- Affects Version/s: 3.1.1 3.1.2 3.1.3 3.1.4 > Stray newline if pretty-printing without xml declaration > > > Key: XERCESC-1902 > URL: https://issues.apache.org/jira/browse/XERCESC-1902 > Project: Xerces-C++ > Issue Type: Bug > Components: DOM >Affects Versions: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4 >Reporter: Boris Kolpackov >Priority: Minor > Fix For: 3.2.0 > > > If we disable writing xml declaration and enable pretty printing, we get a > stray newline at the beginning of the document: > ' > > ... > > ' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Assigned] (XERCESC-2047) Web site content from 3.1 branch should be copied over to trunk before a release from the trunk
[ https://issues.apache.org/jira/browse/XERCESC-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor reassigned XERCESC-2047: - Assignee: Scott Cantor > Web site content from 3.1 branch should be copied over to trunk before a > release from the trunk > --- > > Key: XERCESC-2047 > URL: https://issues.apache.org/jira/browse/XERCESC-2047 > Project: Xerces-C++ > Issue Type: Task > Components: Documentation >Reporter: Scott Cantor >Assignee: Scott Cantor >Priority: Blocker > Fix For: 3.2.0 > > > The "official" web site source is now back in the source tree, and should be > copied from braches/xerces-3.1/doc into trunk/doc when the trunk is to be > released. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Resolved] (XERCESC-1980) type 'derivationControl' not found when using XMLSchema.xsd
[ https://issues.apache.org/jira/browse/XERCESC-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor resolved XERCESC-1980. --- Resolution: Invalid > type 'derivationControl' not found when using XMLSchema.xsd > --- > > Key: XERCESC-1980 > URL: https://issues.apache.org/jira/browse/XERCESC-1980 > Project: Xerces-C++ > Issue Type: Bug > Components: Validating Parser (XML Schema) >Affects Versions: 3.1.1 > Environment: Ubuntu 11.10 Linux default libxerces-c3.1 version > 3.1.1-1build1 Intel 64bit >Reporter: Cezar Andrei >Priority: Critical > > Using Xerces C++ API to load XMLSchema.xsd from > http://www.w3.org/2001/XMLSchema.xsd , I get the following error even if the > type 'derivationControl' is defined later in the same file at line 2082. > "Error in schema with system id file:///home/c/XMLSchema.xsd, line 177, > column 47. > type 'http://www.w3.org/2001/XMLSchema:derivationControl' not found" > There are also several warnings: > Warning at file file:///home/c/XMLSchema.xsd, line 99, char 7 > Message: attribute 'id' has already been declared for element > 'xs:simpleType' > Warning at file file:///home/c/XMLSchema.xsd, line 122, char 7 > Message: attribute 'id' has already been declared for element 'xs:list' > Warning at file file:///home/c/XMLSchema.xsd, line 130, char 7 > Message: attribute 'id' has already been declared for element 'xs:union' > Warning at file file:///home/c/XMLSchema.xsd, line 140, char 20 > Message: attribute 'id' has already been declared for element > 'xs:maxExclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 145, char 20 > Message: attribute 'id' has already been declared for element > 'xs:minExclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 151, char 20 > Message: attribute 'id' has already been declared for element > 'xs:maxInclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 156, char 20 > Message: attribute 'id' has already been declared for element > 'xs:minInclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 162, char 20 > Message: attribute 'id' has already been declared for element > 'xs:totalDigits' > Warning at file file:///home/c/XMLSchema.xsd, line 167, char 20 > Message: attribute 'id' has already been declared for element > 'xs:fractionDigits' > Warning at file file:///home/c/XMLSchema.xsd, line 173, char 20 > Message: attribute 'id' has already been declared for element 'xs:length' > Warning at file file:///home/c/XMLSchema.xsd, line 178, char 20 > Message: attribute 'id' has already been declared for element 'xs:minLength' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Closed] (XERCESC-1980) type 'derivationControl' not found when using XMLSchema.xsd
[ https://issues.apache.org/jira/browse/XERCESC-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor closed XERCESC-1980. - > type 'derivationControl' not found when using XMLSchema.xsd > --- > > Key: XERCESC-1980 > URL: https://issues.apache.org/jira/browse/XERCESC-1980 > Project: Xerces-C++ > Issue Type: Bug > Components: Validating Parser (XML Schema) >Affects Versions: 3.1.1 > Environment: Ubuntu 11.10 Linux default libxerces-c3.1 version > 3.1.1-1build1 Intel 64bit >Reporter: Cezar Andrei >Priority: Critical > > Using Xerces C++ API to load XMLSchema.xsd from > http://www.w3.org/2001/XMLSchema.xsd , I get the following error even if the > type 'derivationControl' is defined later in the same file at line 2082. > "Error in schema with system id file:///home/c/XMLSchema.xsd, line 177, > column 47. > type 'http://www.w3.org/2001/XMLSchema:derivationControl' not found" > There are also several warnings: > Warning at file file:///home/c/XMLSchema.xsd, line 99, char 7 > Message: attribute 'id' has already been declared for element > 'xs:simpleType' > Warning at file file:///home/c/XMLSchema.xsd, line 122, char 7 > Message: attribute 'id' has already been declared for element 'xs:list' > Warning at file file:///home/c/XMLSchema.xsd, line 130, char 7 > Message: attribute 'id' has already been declared for element 'xs:union' > Warning at file file:///home/c/XMLSchema.xsd, line 140, char 20 > Message: attribute 'id' has already been declared for element > 'xs:maxExclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 145, char 20 > Message: attribute 'id' has already been declared for element > 'xs:minExclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 151, char 20 > Message: attribute 'id' has already been declared for element > 'xs:maxInclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 156, char 20 > Message: attribute 'id' has already been declared for element > 'xs:minInclusive' > Warning at file file:///home/c/XMLSchema.xsd, line 162, char 20 > Message: attribute 'id' has already been declared for element > 'xs:totalDigits' > Warning at file file:///home/c/XMLSchema.xsd, line 167, char 20 > Message: attribute 'id' has already been declared for element > 'xs:fractionDigits' > Warning at file file:///home/c/XMLSchema.xsd, line 173, char 20 > Message: attribute 'id' has already been declared for element 'xs:length' > Warning at file file:///home/c/XMLSchema.xsd, line 178, char 20 > Message: attribute 'id' has already been declared for element 'xs:minLength' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Closed] (XERCESC-1932) Using xerces-c_3_1D.dll with files compiled under VS-C++ 9.0 on computer which has VS-c++ 6.0 with libraries of VS-c++9.0
[ https://issues.apache.org/jira/browse/XERCESC-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor closed XERCESC-1932. - > Using xerces-c_3_1D.dll with files compiled under VS-C++ 9.0 on computer > which has VS-c++ 6.0 with libraries of VS-c++9.0 > - > > Key: XERCESC-1932 > URL: https://issues.apache.org/jira/browse/XERCESC-1932 > Project: Xerces-C++ > Issue Type: Bug > Components: Miscellaneous >Affects Versions: 3.1.0 > Environment: Microsoft windows XP professional version 2002 SP2, with > VS-C++ 6.0 installed >Reporter: michael n > Attachments: dllload1.exe, dllload.cpp, dllload.exe, msvcp90.dll, > msvcr90.dll, vcredist_x86.exe, xerces-c_3_0D.dll, xerces-c_3_1D.dll, xer > err.JPG > > > The software was compiled on computer with same operating system but with > VS-C++ 9.0 (2008) installed. > When trying to use the program on a platform with same operating system , but > with VS-c++ 6.0 installed (with xerces-c_3_1D.dll ). > I got the Error: > "(1) Error number 126. search in MSDN Help under "Platform SDK (Windows Basic > Services)" subset, topic "System Errors - Numerical Order". > I guessed its cause is the lack of libraries from VS-c++9.0, so I installed > vcredist_x86.exe from Microsoft site, but of no use. > I Would appreciate your help, > Michael -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Commented] (XERCESC-1902) Stray newline if pretty-printing without xml declaration
[ https://issues.apache.org/jira/browse/XERCESC-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080583#comment-16080583 ] Scott Cantor commented on XERCESC-1902: --- Another issue was filed on this, I must have overlooked the pretty-print factor, as I didn't observe the behavior. > Stray newline if pretty-printing without xml declaration > > > Key: XERCESC-1902 > URL: https://issues.apache.org/jira/browse/XERCESC-1902 > Project: Xerces-C++ > Issue Type: Bug > Components: DOM >Affects Versions: 3.1.0 >Reporter: Boris Kolpackov >Priority: Minor > > If we disable writing xml declaration and enable pretty printing, we get a > stray newline at the beginning of the document: > ' > > ... > > ' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Resolved] (XERCESC-1739) Base64 codec adds LF at the end of last line
[ https://issues.apache.org/jira/browse/XERCESC-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor resolved XERCESC-1739. --- Resolution: Won't Fix There's also no reason to care if it does add one, so changing the behavior is a needless change at this point. > Base64 codec adds LF at the end of last line > > > Key: XERCESC-1739 > URL: https://issues.apache.org/jira/browse/XERCESC-1739 > Project: Xerces-C++ > Issue Type: Bug > Components: Utilities >Affects Versions: 1.6.0, 1.7.0, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0, > 2.6.0, 2.7.0 >Reporter: Vladimir Polegenko >Priority: Minor > > According to RFC2045: > The encoded output stream must be represented in lines of no more than 76 > characters each. All line breaks or other characters not found in Base64 > Alphabet must be ignored by decoding software. In base64 data, characters > other than those in Base64 Alphabet, line breaks, and other white space > probably indicate a transmission error, about which a warning message or even > a message rejection might be appropriate under some circumstances. > Therefore, there is no need to add LF at the end of last line. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Updated] (XERCESC-1902) Stray newline if pretty-printing without xml declaration
[ https://issues.apache.org/jira/browse/XERCESC-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor updated XERCESC-1902: -- Fix Version/s: 3.2.0 > Stray newline if pretty-printing without xml declaration > > > Key: XERCESC-1902 > URL: https://issues.apache.org/jira/browse/XERCESC-1902 > Project: Xerces-C++ > Issue Type: Bug > Components: DOM >Affects Versions: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4 >Reporter: Boris Kolpackov >Priority: Minor > Fix For: 3.2.0 > > > If we disable writing xml declaration and enable pretty printing, we get a > stray newline at the beginning of the document: > ' > > ... > > ' -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Closed] (XERCESC-1836) Add SVN revsion number to version number
[ https://issues.apache.org/jira/browse/XERCESC-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor closed XERCESC-1836. - > Add SVN revsion number to version number > > > Key: XERCESC-1836 > URL: https://issues.apache.org/jira/browse/XERCESC-1836 > Project: Xerces-C++ > Issue Type: Improvement > Components: Build >Affects Versions: 3.0.0 > Environment: MS Windows XP SP3, VS2005/8 >Reporter: David Kelvin >Priority: Minor > > A number of Open Source projects, that generate executables and DLL files, > add the SVN version number to the version displayed via properties [I don't > know if the equivalent is available for non-Windows platforms]. > This is normally done in the custom Pre-Build step that uses TortoiseSVN's > "SubWCRev.exe" program to copy a file (e.g. version.in) to a new file > (version.h) which defines the current revision level. This is included in > the corresponding resource file so that it is visible to the user. See > project http://passwordsafe.sourceforge.net/ as an example. > So with the current level: the propery page would show the DLL was > 3.0.0.708302. > I think this would be useful when an application wanted to make sure that the > version in use has a specific fix included prior to a formal release. > Thanks. > David -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Resolved] (XERCESC-1836) Add SVN revsion number to version number
[ https://issues.apache.org/jira/browse/XERCESC-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor resolved XERCESC-1836. --- Resolution: Won't Do Not aware of any demand for this and anybody doing a build of unreleased code can change it anyway they like. > Add SVN revsion number to version number > > > Key: XERCESC-1836 > URL: https://issues.apache.org/jira/browse/XERCESC-1836 > Project: Xerces-C++ > Issue Type: Improvement > Components: Build >Affects Versions: 3.0.0 > Environment: MS Windows XP SP3, VS2005/8 >Reporter: David Kelvin >Priority: Minor > > A number of Open Source projects, that generate executables and DLL files, > add the SVN version number to the version displayed via properties [I don't > know if the equivalent is available for non-Windows platforms]. > This is normally done in the custom Pre-Build step that uses TortoiseSVN's > "SubWCRev.exe" program to copy a file (e.g. version.in) to a new file > (version.h) which defines the current revision level. This is included in > the corresponding resource file so that it is visible to the user. See > project http://passwordsafe.sourceforge.net/ as an example. > So with the current level: the propery page would show the DLL was > 3.0.0.708302. > I think this would be useful when an application wanted to make sure that the > version in use has a specific fix included prior to a formal release. > Thanks. > David -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
