| Author |
Message |
Forum: DCMTK - General Topic: How to query DCMTK version |
| J. Riesmeier |
|
Posted: Fri, 2018-09-14, 08:06
|
|
Replies: 1
Views: 28
|
| There is a macro OFFIS_DCMTK_VERSION in "dcmtk/dcmdata/dcuid.h". |
|
 |
Forum: DCMTK - General Topic: Exact Difference between MR and Enhanced MR Image Storage |
| J. Riesmeier |
|
Posted: Tue, 2018-09-11, 20:20
|
|
Replies: 1
Views: 25
|
| Where exactly is the DCMTK-related aspect in your question? |
|
|
Forum: DCMTK - General Topic: DSRTypes::checkForValidReference too strict ? |
| J. Riesmeier |
|
Posted: Mon, 2018-09-10, 10:06
|
|
Replies: 3
Views: 40
|
| Yes - I was assuming that it should check for UIDs. I think I used to use a UID test function, and I changed it to this whilst upgrading to DCMTK 3.6.3. There are other methods that check a given UID for validity, both in DCMTK's dcmdata and dcmsr module. Worse than that, I think that I am using th... |
|
|
Forum: DCMTK - General Topic: DSRTypes::checkForValidReference too strict ? |
| J. Riesmeier |
|
Posted: Sun, 2018-09-09, 12:30
|
|
Replies: 3
Views: 40
|
| The purpose of DSRTypes::checkForValidReference() is not to check Unique Identifiers (UID) as you seem to assume. The documentation clearly says: "check string for valid reference (as used for by-reference relationships)". Therefore, your sample string is invalid. See DICOM PS3.3 Section C... |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Thu, 2018-09-06, 08:06
|
|
Replies: 20
Views: 203
|
| As I wrote in my previous posting, "ISO 2022 IR 87" is only used for character sets with code extensions, which requires to provide multiple values in the Specific Character Set (0008,0005) attribute. For example, "ISO 2022 IR 13\ISO 2022 IR 87" would be a valid value. |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Wed, 2018-09-05, 16:51
|
|
Replies: 20
Views: 203
|
| Short answer: according to the DICOM standard, 'ISO 2022 IR 87' is only allowed for character sets with code extensions, i.e. if multiple values are given in the Specific Character Set (0008,0005) attribute. For Japanese characters without code extensions (ISO 2022), you have to use 'ISO_IR 13' as t... |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Tue, 2018-09-04, 12:16
|
|
Replies: 20
Views: 203
|
Quote: Not showing the option and external library.
Then, ICU is not properly enabled. Maybe, you should re-build the DCMTK. |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Tue, 2018-09-04, 11:48
|
|
Replies: 20
Views: 203
|
When you compile DCMTK with ICU enabled, does dcmdump provide a --convert-to-utf8 option and does dcmdump --version show ICU as an "external libraries used"?
How did you integrate support for DCMTK into your own application? |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Tue, 2018-09-04, 11:09
|
|
Replies: 20
Views: 203
|
| And what is the value of DCMTK_ENABLE_CHARSET_CONVERSION after CMake performed the configure step? Is the CMake variable DCMTK_WITH_ICU set to "ON"? |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Mon, 2018-09-03, 18:02
|
|
Replies: 20
Views: 203
|
| As I said, you can use DcmDataset::convertToUTF8() to convert the entire DICOM dataset of the C-FIND request from any character set that is defined by the DICOM standard (e.g. Japanese) to Unicode (UTF-8). After this conversion, you can access the Patient's Name (0010,0010), which is now encoded in ... |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Mon, 2018-09-03, 14:51
|
|
Replies: 20
Views: 203
|
| Could you please provide more details on your use case? DCMTK supports all Specific Character Sets that are defined by the DICOM standard, at least for input. With "query a japanese patient name from db" you mean what? |
|
|
Forum: DCMTK - General Topic: Unicode conversion |
| J. Riesmeier |
|
Posted: Mon, 2018-09-03, 14:16
|
|
Replies: 20
Views: 203
|
| If DCMTK is compiled with character set conversion enabled (requires one of the supported conversion libraries), you could simply call convertToUTF8() on the DcmDataset instance. |
|
|
Forum: DCMTK - General Topic: Adding images to SR |
| J. Riesmeier |
|
Posted: Fri, 2018-08-17, 08:06
|
|
Replies: 5
Views: 152
|
| The relationship type is "INFERRED FROM" and not "R-INFERRED FROM", so it is by value (and not by reference), i.e. you could use addContentItem(). |
|
|
Forum: DCMPRINT Topic: Re-printing stored print objects |
| J. Riesmeier |
|
Posted: Tue, 2018-08-14, 18:26
|
|
Replies: 13
Views: 210
|
| Somebody from OFFIS should answer this since DCMPRINT is not part of the public DCMTK... maybe, it works if you register the SP and HG files to the "index.dat" with the tool "dcmqridx". |
|
|
Forum: DCMPRINT Topic: Re-printing stored print objects |
| J. Riesmeier |
|
Posted: Tue, 2018-08-14, 17:33
|
|
Replies: 13
Views: 210
|
| The Stored Print object does not contain the images (Pixel Data). That's why you also need the Hardcopy Grayscale Images. Create all required files with dcmpsprt and you should be fine. |
|
|
| Sort by: |
Login
FAQ
Search
Members