[Bug 66085] New: org.openxmlformats.schemas.wordprocessingml.x2006.main.STHint missing ENUM value

2022-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66085

Bug ID: 66085
   Summary: org.openxmlformats.schemas.wordprocessingml.x2006.main
.STHint missing ENUM value
   Product: POI
   Version: unspecified
  Hardware: PC
Status: NEW
  Severity: normal
  Priority: P2
 Component: XWPF
  Assignee: dev@poi.apache.org
  Reporter: chrisl...@hotmail.com
  Target Milestone: ---

Created attachment 38302
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=38302=edit
Failing Word Doc

Hi,

I'm not sure this is strictly the correct place to log this, but I don't know
where else to go.

We are currently attempting an upgrade of POI from v4.1.2 to v5.2.2. In this we
note in your release notes that this includes an update in conformance to the
ECMA-376 fifth edition spec. With the updated libraries, running the attached
Word Document we received an unexpected error:

string value 'cs' is not a valid enumeration value for ST_Hint in namespace
http://schemas.openxmlformats.org/wordprocessingml/2006/main.
  org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: string value
'cs' is not a valid enumeration value for ST_Hint in namespace
http://schemas.openxmlformats.org/wordprocessingml/2006/main

Having investigated this, I see that it's not really a problem with POI per se.
According to the PDF of the spec:
  Ecma Office Open XML Part 1 - Fundamentals And Markup Language Reference.pdf
- 17.18.41 ST_Hint (Font Type Hint) p.1396 (page 1406)
  cs (Complex Script Font) is mentioned as a possible value
- A.1 WordprocessingML p.3841 (page 3851)
  Line 1715 of the XSD shows 'cs' as a possible value.

However, in the actual XSD used to generate the XMLBeans classes:
  ECMA-376-Fifth-Edition-Part-4-Transitional-Migration-Features.zip
- OfficeOpenXML-XMLSchema-Transitional.zip
  - wml.xsd
Line 1789 of the XSD there is no STHint.CS ENUM and thus no ENUM in the
code generated by XMLBeans.

So I can see that the POI classes are simply conforming to the XSD via XMLBeans
generation. For now we can work around this fact, but is this something you
guys are able to modify/fix as part of your processes?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



Re: xmlbeans 5.1.0 release

2022-05-23 Thread Dominik Stadler
+1

Dominik.

On Mon, May 23, 2022 at 5:22 PM PJ Fanning 
wrote:

> Hi everyone,
> There are a fair number of unreleased changes in XMLBeans. Is it time for
> a v5.1.0 release?
>
>
> https://issues.apache.org/jira/browse/XMLBEANS-604?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%205.1.0%22
>
> I can put together an RC if there are no objections.
>
> Regards,
> PJ
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>


xmlbeans 5.1.0 release

2022-05-23 Thread PJ Fanning
Hi everyone,
There are a fair number of unreleased changes in XMLBeans. Is it time for a 
v5.1.0 release?

https://issues.apache.org/jira/browse/XMLBEANS-604?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%205.1.0%22

I can put together an RC if there are no objections.

Regards,
PJ

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[Bug 66083] support CEILING.MATH and FLOOR.MATH functions

2022-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66083

PJ Fanning  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[Bug 66083] support CEILING.MATH and FLOOR.MATH functions

2022-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66083

--- Comment #1 from PJ Fanning  ---
I have added changes today for this

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[Bug 66083] New: support CEILING.MATH and FLOOR.MATH functions

2022-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66083

Bug ID: 66083
   Summary: support CEILING.MATH and FLOOR.MATH functions
   Product: POI
   Version: 5.2.2-FINAL
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: SS Common
  Assignee: dev@poi.apache.org
  Reporter: fannin...@yahoo.com
  Target Milestone: ---

https://support.microsoft.com/en-us/office/floor-math-function-c302b599-fbdb-4177-ba19-2c2b1249a2f5

https://support.microsoft.com/en-us/office/ceiling-math-function-80f95d2f-b499-4eee-9f16-f795a8e306c8

Also - add missing test cases for legacy floor and math functions

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[GitHub] [poi] asfgit closed pull request #331: chore: Included githubactions in the dependabot config

2022-05-23 Thread GitBox


asfgit closed pull request #331: chore: Included githubactions in the 
dependabot config
URL: https://github.com/apache/poi/pull/331


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[Bug 66022] FormulaParseException: Parse error near char 0

2022-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66022

--- Comment #5 from PJ Fanning  ---
added patch with r1901162 - will see what happens with CI build before
proceeding with any further changes

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[Bug 66022] FormulaParseException: Parse error near char 0

2022-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66022

renfi...@yahoo.com changed:

   What|Removed |Added

 Status|NEEDINFO|NEW

--- Comment #4 from renfi...@yahoo.com ---
I also came across this bug.

The problematic method seems to be FormulaParser:parseSheetName.

In the patch I added unit tests which trigger this bug and also added a first
try for a fix.
Tested the fix for the file provided by max (by opening it in unit test and
shifting a row). Worked for me with fix.


Additional issue: In 'TestXSSFFormulaParser:testQuotedSheetNamesReference' I
also added a uncommented test-case, which does not work with or without the
fix. Problem there is also related to FormulaParser:parseSheetName. Additional
"'" get added around sheet-name. Since I am new to POI-library, I can not tell
if this is actually is a problem or not. 

Hope someone with more experience in this area, can resolve these issue(s).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[Bug 66022] FormulaParseException: Parse error near char 0

2022-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66022

--- Comment #3 from renfi...@yahoo.com ---
Created attachment 38300
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=38300=edit
unit tests and first try for fix

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org



[jira] [Commented] (XMLBEANS-567) Problems with XMLBeans Extension Interfaces Feature

2022-05-23 Thread Peter Keller (Jira)


[ 
https://issues.apache.org/jira/browse/XMLBEANS-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540834#comment-17540834
 ] 

Peter Keller commented on XMLBEANS-567:
---

[~pj.fanning] My simple test case works fine for me with the new JAR. It 
doesn't work with my existing project that I would like to migrate from 3.1.0 
because of memory usage problems in JavaParser, but that is a completely 
separate issue of course.

> Problems with XMLBeans Extension Interfaces Feature
> ---
>
> Key: XMLBEANS-567
> URL: https://issues.apache.org/jira/browse/XMLBEANS-567
> Project: XMLBeans
>  Issue Type: Task
>Affects Versions: Version 5.0.0
>Reporter: Dmitry Lastochkin
>Priority: Major
> Fix For: Version 5.1.0
>
> Attachments: xmlbeans-ie-tryout.tar, xmlbeans-ie-tryout2.tar
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Hello! In our project we are using [XMLBeans Extension Interfaces 
> Feature|https://cwiki.apache.org/confluence/display/XMLBEANS/ExtensionInterfacesFeature].
>  When we compile the TypeSystem (using {{SchemaTypeSystemCompiler.compile}}), 
> we add the jar with our extension classes to classpath parameter. In XMLBeans 
> 2.4 it works perfectly. But when we updated to XMLBeans 5.0.0, we encountered 
> the following error during an extensions validation:
> {code}
> Interface 'SomeInterface' not found."
> {code}
> As far as I understand, this is because 
> {{org.apache.xmlbeans.impl.config.Parser}} does not search classes in 
> classpath (only in files). 
> When we added the sources of the extension interface to the parameters, 
> TypeSystem compiled successfuly. But then we ran into another problem. When 
> XMLBeans generates java files from XSD, it uses simple class names (instead 
> of fully qualified names as it was in XMLBeans 2.4.0) for the classes that 
> are used in methods of the extension interface (like parameters types or 
> return types). And therefore the geneted files cannot be compiled if the 
> extension classes are in a different package.
> Are those changes (ingorning classpath when searching for extenstions  and 
> using simple names for extenstion classes in code generation instead of fully 
> qualified names) were made intentionally? Such limitations are hard to work 
> around, making an upgrade from older XMLBeans version very complicated.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org