Project

General

Profile

Actions
Copy link

Feature #425

closed

DCMTK does not compile with UNICODE / _UNICODE defined (Windows only)

Added by Jörg Riesmeier over 13 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Marco Eichelberg
Category:
Library
Target version:
-
Start date:
2012-05-24
Due date:
% Done:

100%

Estimated time:
5:00 h
Module:
all
Operating System:
Compiler:

Description

Currently, DCMTK does not take care of the defines UNICODE / _UNICODE, which are used for the "wide char" API on Windows. In other words, DCMTK currently does not compile when these defines are specified (e.g. Visual Studio 2008 Express).

See e.g. http://msdn.microsoft.com/en-us/library/ff381407(v=vs.85).aspx

Related issues 1 (1 open — 0 closed)

Related to DCMTK - Feature #543: Check whether "oflog" supports character set conversionNew2013-08-15

Actions
Actions
Copy link
 #1

Updated by Jörg Riesmeier about 13 years ago

For now, a comment has been added to the INSTALL file:

Known limitations of DCMTK on the Windows platform.

[...]

5. DCMTK does not compile when UNICODE or _UNICODE is defined because the
   VisualStudio compiler then uses the Unicode version instead of the ANSI
   version for all Windows API functions (i.e. type wchar_t instead of char
   for all character string parameters and return values).
Actions
Copy link
 #2

Updated by Jörg Riesmeier about 13 years ago

  • Tracker changed from Bug to Feature
Actions
Copy link
 #3

Updated by Pedro Fernando Arizpe Gómez over 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Pedro Fernando Arizpe Gómez
Actions
Copy link
 #4

Updated by Jörg Riesmeier about 6 years ago

  • Related to Feature #543: Check whether "oflog" supports character set conversion added
Actions
Copy link
 #5

Updated by Jörg Riesmeier about 6 years ago

With commit b55e5e1 the internal XML parser (ofxml) has been enabled to support "wide characters". However, by defining the macro WIDE_CHAR_XML_PARSER, the class DcmEncapsulatedDocument and the tool cda2dcm loose the ability to parse CDA data (since the API of the parser becomes incompatible) and become useless. pdf2dcm and stl2dcm should still work as expected.

This issue should also be fixed when enabling support for UNICODE / _UNICODE.

Actions
Copy link
 #6

Updated by Marco Eichelberg over 5 years ago

  • Subject changed from DCMTK does not compile with UNICODE / _UNICODE defined (Windows only?) to DCMTK does not compile with UNICODE / _UNICODE defined (Windows only)
  • Status changed from Assigned to Closed
  • Assignee changed from Pedro Fernando Arizpe Gómez to Marco Eichelberg
  • % Done changed from 0 to 100
  • Estimated time set to 5:00 h

Closed by commit #621d553e8 (public modules) and 3aa1fcb67 (private modules).

Note: UNICODE/_UNICODE does not implicitly activate the wide-char mode in ofxml anymore. When this is actively activated by the used by defining WIDE_CHAR_XML_PARSER at compile time, a compiler warning will be printed indicating that cda2dcm will not work.

Actions
Copy link

Also available in: Atom PDF