[
https://issues.apache.org/jira/browse/DIRSTUDIO-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526854#comment-17526854
]
Fredrik Roubert commented on DIRSTUDIO-1296:
--------------------------------------------
In case you haven't seen it already, I've uploaded this PR with a proposed fix:
[https://github.com/apache/directory-studio/pull/32]
It only affects export to spreadsheet (CSV, Excel, ODF) file formats, which
Directory Studio itself can't import directly and if you were to copy-paste a
cell with a postal address with line breaks in it from your spreadsheet
application into the Directory Studio postal address value editor, it'll then
become properly encoded again when stored in LDAP again.
> Export doesn't decode RFC 4517 Postal Address syntax
> ----------------------------------------------------
>
> Key: DIRSTUDIO-1296
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1296
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
> Affects Versions: 2.0.0-M17
> Reporter: Fredrik Roubert
> Priority: Major
>
> When exporting any entries using the RFC 4517 Postal Address syntax
> (1.3.6.1.4.1.1466.115.121.1.41) to any non-LDAP data format (CSV, Excel, …)
> these entries aren't decoded but the RFC 4517 escaped data is instead
> exported as-is, like this:
> \241,000,000 Sweepstakes$PO Box 1000000$Anytown, CA 12345$USA
> … instead of this:
> $1,000,000 Sweepstakes
> {{PO Box 1000000}}
> {{Anytown, CA 12345}}
> {{USA}}
> I think it's safe to assume that no non-LDAP software is expected to be able
> to decode RFC 4517 escaped data, so not doing this decoding upon export must
> be a bug.
> (This data is correctly decoded and encoded by default for display and edit
> within Directory Studio itself.)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
