Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

about two bug at the new version abap2xlsx #678

Closed
syjf1976 opened this issue Jul 15, 2020 · 3 comments
Closed

about two bug at the new version abap2xlsx #678

syjf1976 opened this issue Jul 15, 2020 · 3 comments

Comments

@syjf1976
Copy link

I find two bugs in this new version.
the first one is : don't support asia language such as chinese. and the bug is because the class ZCL_EXCEL_WRITER_2007 method RENDER_XML_DOCUMENT . the follow code skip asia language character. It's FINE if block these code.

  • TRY.
  •  CALL METHOD lo_ostream->('SKIP_NON_XML_CHARACTERS')
    
  •    EXPORTING
    
  •      is_skipping = abap_true.
    
  • CATCH cx_sy_dyn_call_illegal_method.
  • ENDTRY.
    the second one is : If an internal table have integer field. a short dump will display be bug is because class ZCL_EXCEL_WORKSHEET method SET_CELL
    CASE lv_value_type.
    WHEN cl_abap_typedescr=>typekind_int1 OR cl_abap_typedescr=>typekind_int1 OR cl_abap_typedescr=>typekind_int2
    OR <fs_typekind_int8>. "Allow INT8 types columns
    changed to
    CASE lv_value_type.
    WHEN cl_abap_typedescr=>typekind_int OR cl_abap_typedescr=>typekind_int1 OR cl_abap_typedescr=>typekind_int2
    OR <fs_typekind_int8>. "Allow INT8 types columns
@bigld
Copy link
Collaborator

bigld commented Jul 21, 2020

introduced with #298

@sandraros
Copy link
Collaborator

Unicode not rendered should now be fixed (#756). Could you tell us if it's okay for you? Thanks.

@sandraros
Copy link
Collaborator

No answer. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants