Unicode symbols in iTextSharp relative link
I'm trying to create a relative link in pdf file created with iTextSharp
everything works good with ASCII letters, but if I add other unicode symbols in path they are just skipped
This works fine:
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Attachments/1.jpg");
This creates incorrect link (link is created like this: //1.jpg, Вложения - part is missing):
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Вложения/1.jpg");
Is there any way to create correct link with unicode symbols?
Thanks
c# pdf unicode itext
asked Nov 12 at 14:42
Olja Muravjova
104
|
show 2 more comments
I'm trying to create a relative link in pdf file created with iTextSharp
everything works good with ASCII letters, but if I add other unicode symbols in path they are just skipped
This works fine:
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Attachments/1.jpg");
This creates incorrect link (link is created like this: //1.jpg, Вложения - part is missing):
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Вложения/1.jpg");
Is there any way to create correct link with unicode symbols?
Thanks
c# pdf unicode itext
asked Nov 12 at 14:42
Olja Muravjova
104
Do you have that correct font installed on the machine performing the pdf conversion? It sounds like you are missing the needed font.
– Ross Bush
Nov 12 at 14:49
@RossBush I don't understand what do you mean by font installed? These kind of paths are supported in file managers on my computer
– Olja Muravjova
Nov 12 at 15:03
Some fonts like WingDings2 may or may not be installed on the server that is rendering the text. If there is a missing font you will oftentimes see odd squares or other anomalies. What OS are you using to render the PDF?
– Ross Bush
Nov 12 at 17:10
1
@RossBush I used Arial there, however, this font is used to write "text" parameter in pdf and there is no problem with that, the problem is with the link "behind" this text
– Olja Muravjova
Nov 12 at 21:44
1
I am sorry Ross, but you are on a wild goose chase. The font has nothing to do with it. I am more thinking along the lines of the pdf specification being difficult about non-ascii characters in link destinations. I don't know, I'd have to look it up in the pdf reference we have at the office and I am sure that my colleagues wouldn't even have to look it up, but I am quite convinced that a link destination does not have a font.
– Amedee Van Gasse
Nov 13 at 5:33
|
show 2 more comments
I'm trying to create a relative link in pdf file created with iTextSharp
everything works good with ASCII letters, but if I add other unicode symbols in path they are just skipped
This works fine:
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Attachments/1.jpg");
This creates incorrect link (link is created like this: //1.jpg, Вложения - part is missing):
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Вложения/1.jpg");
Is there any way to create correct link with unicode symbols?
Thanks
c# pdf unicode itext
asked Nov 12 at 14:42
Olja Muravjova
104
I'm trying to create a relative link in pdf file created with iTextSharp
everything works good with ASCII letters, but if I add other unicode symbols in path they are just skipped
This works fine:
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Attachments/1.jpg");
This creates incorrect link (link is created like this: //1.jpg, Вложения - part is missing):
Chunk chunk = new Chunk(text, font);
chunk.SetAnchor("./Вложения/1.jpg");
Is there any way to create correct link with unicode symbols?
Thanks
c# pdf unicode itext
c# pdf unicode itext
asked Nov 12 at 14:42
Olja Muravjova
104
asked Nov 12 at 14:42
Olja Muravjova
104
asked Nov 12 at 14:42
Olja Muravjova
104
asked Nov 12 at 14:42
Olja Muravjova
104
asked Nov 12 at 14:42
Olja Muravjova
104
104
Do you have that correct font installed on the machine performing the pdf conversion? It sounds like you are missing the needed font.
– Ross Bush
Nov 12 at 14:49
@RossBush I don't understand what do you mean by font installed? These kind of paths are supported in file managers on my computer
– Olja Muravjova
Nov 12 at 15:03
Some fonts like WingDings2 may or may not be installed on the server that is rendering the text. If there is a missing font you will oftentimes see odd squares or other anomalies. What OS are you using to render the PDF?
– Ross Bush
Nov 12 at 17:10
1
@RossBush I used Arial there, however, this font is used to write "text" parameter in pdf and there is no problem with that, the problem is with the link "behind" this text
– Olja Muravjova
Nov 12 at 21:44
1
I am sorry Ross, but you are on a wild goose chase. The font has nothing to do with it. I am more thinking along the lines of the pdf specification being difficult about non-ascii characters in link destinations. I don't know, I'd have to look it up in the pdf reference we have at the office and I am sure that my colleagues wouldn't even have to look it up, but I am quite convinced that a link destination does not have a font.
– Amedee Van Gasse
Nov 13 at 5:33
|
show 2 more comments
Do you have that correct font installed on the machine performing the pdf conversion? It sounds like you are missing the needed font.
– Ross Bush
Nov 12 at 14:49
@RossBush I don't understand what do you mean by font installed? These kind of paths are supported in file managers on my computer
– Olja Muravjova
Nov 12 at 15:03
Some fonts like WingDings2 may or may not be installed on the server that is rendering the text. If there is a missing font you will oftentimes see odd squares or other anomalies. What OS are you using to render the PDF?
– Ross Bush
Nov 12 at 17:10
1
@RossBush I used Arial there, however, this font is used to write "text" parameter in pdf and there is no problem with that, the problem is with the link "behind" this text
– Olja Muravjova
Nov 12 at 21:44
1
I am sorry Ross, but you are on a wild goose chase. The font has nothing to do with it. I am more thinking along the lines of the pdf specification being difficult about non-ascii characters in link destinations. I don't know, I'd have to look it up in the pdf reference we have at the office and I am sure that my colleagues wouldn't even have to look it up, but I am quite convinced that a link destination does not have a font.
– Amedee Van Gasse
Nov 13 at 5:33
Do you have that correct font installed on the machine performing the pdf conversion? It sounds like you are missing the needed font.
– Ross Bush
Nov 12 at 14:49
Do you have that correct font installed on the machine performing the pdf conversion? It sounds like you are missing the needed font.
– Ross Bush
Nov 12 at 14:49
@RossBush I don't understand what do you mean by font installed? These kind of paths are supported in file managers on my computer
– Olja Muravjova
Nov 12 at 15:03
@RossBush I don't understand what do you mean by font installed? These kind of paths are supported in file managers on my computer
– Olja Muravjova
Nov 12 at 15:03
Some fonts like WingDings2 may or may not be installed on the server that is rendering the text. If there is a missing font you will oftentimes see odd squares or other anomalies. What OS are you using to render the PDF?
– Ross Bush
Nov 12 at 17:10
Some fonts like WingDings2 may or may not be installed on the server that is rendering the text. If there is a missing font you will oftentimes see odd squares or other anomalies. What OS are you using to render the PDF?
– Ross Bush
Nov 12 at 17:10
1
1
@RossBush I used Arial there, however, this font is used to write "text" parameter in pdf and there is no problem with that, the problem is with the link "behind" this text
– Olja Muravjova
Nov 12 at 21:44
@RossBush I used Arial there, however, this font is used to write "text" parameter in pdf and there is no problem with that, the problem is with the link "behind" this text
– Olja Muravjova
Nov 12 at 21:44
1
1
I am sorry Ross, but you are on a wild goose chase. The font has nothing to do with it. I am more thinking along the lines of the pdf specification being difficult about non-ascii characters in link destinations. I don't know, I'd have to look it up in the pdf reference we have at the office and I am sure that my colleagues wouldn't even have to look it up, but I am quite convinced that a link destination does not have a font.
– Amedee Van Gasse
Nov 13 at 5:33
I am sorry Ross, but you are on a wild goose chase. The font has nothing to do with it. I am more thinking along the lines of the pdf specification being difficult about non-ascii characters in link destinations. I don't know, I'd have to look it up in the pdf reference we have at the office and I am sure that my colleagues wouldn't even have to look it up, but I am quite convinced that a link destination does not have a font.
– Amedee Van Gasse
Nov 13 at 5:33
|
show 2 more comments
1 Answer
1
active
oldest
votes
By using Chunk.SetAnchor in iText 5 you effectively generate an URI Action. The URI parameter thereof is specified as
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in 7-bit ASCII.
(ISO 32000-1, Table 206 – Additional entries specific to a URI action)
Thus, it can be considered ok that non-ASCII characters like your Cyrillic ones are not accepted by Chunk.SetAnchor. (It is not ok, though, that they are simply dropped; if the method does not accept its input, it should throw an exception.)
But by no means does that mean you cannot reference a file in a path that is using some non-ASCII characters. Instead you can make use of the fact that the path is considered an URI: This in particular means that you can apply the URL encoding scheme for special characters!
Thus, simply replace
chunk.SetAnchor("./Вложения/1.jpg");
by
chunk.SetAnchor(WebUtility.UrlEncode("./Вложения/1.jpg"));
and your link works again! (At least it did in my tests.)
PS: In .Net you actually have quite a choice of classes to do the URL encoding, cf. for example this answer. WebUtility.UrlEncode worked for me in the case at hand but depending on your use case one of the others might be more appropriate.
PPS: The situation changes a bit in the newer PDF specification:
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in UTF8.
(ISO 32000-2, Table 210 — Additional entries specific to a URI action)
(I think the "ASCII" in the type column is a specification error and the UTF8 in the value column is to be taken seriously.)
But iText 5 has no PDF 2.0 support and, therefore, does not support UTF8 encoding here. One should probably test with iText 7 which claims PDF 2.0 support...
answered Nov 14 at 14:52
mkl
52.5k1166144
Thank you, that worked for me. I usedSystem.Web.HttpUtility.UrlPathEncode, because I use .Net 4.0
– Olja Muravjova
Nov 15 at 10:55
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264518%2funicode-symbols-in-itextsharp-relative-link%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
By using Chunk.SetAnchor in iText 5 you effectively generate an URI Action. The URI parameter thereof is specified as
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in 7-bit ASCII.
(ISO 32000-1, Table 206 – Additional entries specific to a URI action)
Thus, it can be considered ok that non-ASCII characters like your Cyrillic ones are not accepted by Chunk.SetAnchor. (It is not ok, though, that they are simply dropped; if the method does not accept its input, it should throw an exception.)
But by no means does that mean you cannot reference a file in a path that is using some non-ASCII characters. Instead you can make use of the fact that the path is considered an URI: This in particular means that you can apply the URL encoding scheme for special characters!
Thus, simply replace
chunk.SetAnchor("./Вложения/1.jpg");
by
chunk.SetAnchor(WebUtility.UrlEncode("./Вложения/1.jpg"));
and your link works again! (At least it did in my tests.)
PS: In .Net you actually have quite a choice of classes to do the URL encoding, cf. for example this answer. WebUtility.UrlEncode worked for me in the case at hand but depending on your use case one of the others might be more appropriate.
PPS: The situation changes a bit in the newer PDF specification:
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in UTF8.
(ISO 32000-2, Table 210 — Additional entries specific to a URI action)
(I think the "ASCII" in the type column is a specification error and the UTF8 in the value column is to be taken seriously.)
But iText 5 has no PDF 2.0 support and, therefore, does not support UTF8 encoding here. One should probably test with iText 7 which claims PDF 2.0 support...
answered Nov 14 at 14:52
mkl
52.5k1166144
Thank you, that worked for me. I usedSystem.Web.HttpUtility.UrlPathEncode, because I use .Net 4.0
– Olja Muravjova
Nov 15 at 10:55
add a comment |
By using Chunk.SetAnchor in iText 5 you effectively generate an URI Action. The URI parameter thereof is specified as
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in 7-bit ASCII.
(ISO 32000-1, Table 206 – Additional entries specific to a URI action)
Thus, it can be considered ok that non-ASCII characters like your Cyrillic ones are not accepted by Chunk.SetAnchor. (It is not ok, though, that they are simply dropped; if the method does not accept its input, it should throw an exception.)
But by no means does that mean you cannot reference a file in a path that is using some non-ASCII characters. Instead you can make use of the fact that the path is considered an URI: This in particular means that you can apply the URL encoding scheme for special characters!
Thus, simply replace
chunk.SetAnchor("./Вложения/1.jpg");
by
chunk.SetAnchor(WebUtility.UrlEncode("./Вложения/1.jpg"));
and your link works again! (At least it did in my tests.)
PS: In .Net you actually have quite a choice of classes to do the URL encoding, cf. for example this answer. WebUtility.UrlEncode worked for me in the case at hand but depending on your use case one of the others might be more appropriate.
PPS: The situation changes a bit in the newer PDF specification:
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in UTF8.
(ISO 32000-2, Table 210 — Additional entries specific to a URI action)
(I think the "ASCII" in the type column is a specification error and the UTF8 in the value column is to be taken seriously.)
But iText 5 has no PDF 2.0 support and, therefore, does not support UTF8 encoding here. One should probably test with iText 7 which claims PDF 2.0 support...
answered Nov 14 at 14:52
mkl
52.5k1166144
Thank you, that worked for me. I usedSystem.Web.HttpUtility.UrlPathEncode, because I use .Net 4.0
– Olja Muravjova
Nov 15 at 10:55
add a comment |
By using Chunk.SetAnchor in iText 5 you effectively generate an URI Action. The URI parameter thereof is specified as
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in 7-bit ASCII.
(ISO 32000-1, Table 206 – Additional entries specific to a URI action)
Thus, it can be considered ok that non-ASCII characters like your Cyrillic ones are not accepted by Chunk.SetAnchor. (It is not ok, though, that they are simply dropped; if the method does not accept its input, it should throw an exception.)
But by no means does that mean you cannot reference a file in a path that is using some non-ASCII characters. Instead you can make use of the fact that the path is considered an URI: This in particular means that you can apply the URL encoding scheme for special characters!
Thus, simply replace
chunk.SetAnchor("./Вложения/1.jpg");
by
chunk.SetAnchor(WebUtility.UrlEncode("./Вложения/1.jpg"));
and your link works again! (At least it did in my tests.)
PS: In .Net you actually have quite a choice of classes to do the URL encoding, cf. for example this answer. WebUtility.UrlEncode worked for me in the case at hand but depending on your use case one of the others might be more appropriate.
PPS: The situation changes a bit in the newer PDF specification:
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in UTF8.
(ISO 32000-2, Table 210 — Additional entries specific to a URI action)
(I think the "ASCII" in the type column is a specification error and the UTF8 in the value column is to be taken seriously.)
But iText 5 has no PDF 2.0 support and, therefore, does not support UTF8 encoding here. One should probably test with iText 7 which claims PDF 2.0 support...
answered Nov 14 at 14:52
mkl
52.5k1166144
By using Chunk.SetAnchor in iText 5 you effectively generate an URI Action. The URI parameter thereof is specified as
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in 7-bit ASCII.
(ISO 32000-1, Table 206 – Additional entries specific to a URI action)
Thus, it can be considered ok that non-ASCII characters like your Cyrillic ones are not accepted by Chunk.SetAnchor. (It is not ok, though, that they are simply dropped; if the method does not accept its input, it should throw an exception.)
But by no means does that mean you cannot reference a file in a path that is using some non-ASCII characters. Instead you can make use of the fact that the path is considered an URI: This in particular means that you can apply the URL encoding scheme for special characters!
Thus, simply replace
chunk.SetAnchor("./Вложения/1.jpg");
by
chunk.SetAnchor(WebUtility.UrlEncode("./Вложения/1.jpg"));
and your link works again! (At least it did in my tests.)
PS: In .Net you actually have quite a choice of classes to do the URL encoding, cf. for example this answer. WebUtility.UrlEncode worked for me in the case at hand but depending on your use case one of the others might be more appropriate.
PPS: The situation changes a bit in the newer PDF specification:
URI
ASCII string
(Required) The uniform resource identifier to resolve, encoded in UTF8.
(ISO 32000-2, Table 210 — Additional entries specific to a URI action)
(I think the "ASCII" in the type column is a specification error and the UTF8 in the value column is to be taken seriously.)
But iText 5 has no PDF 2.0 support and, therefore, does not support UTF8 encoding here. One should probably test with iText 7 which claims PDF 2.0 support...
answered Nov 14 at 14:52
mkl
52.5k1166144
answered Nov 14 at 14:52
mkl
52.5k1166144
answered Nov 14 at 14:52
mkl
52.5k1166144
answered Nov 14 at 14:52
mkl
52.5k1166144
52.5k1166144
Thank you, that worked for me. I usedSystem.Web.HttpUtility.UrlPathEncode, because I use .Net 4.0
– Olja Muravjova
Nov 15 at 10:55
add a comment |
Thank you, that worked for me. I usedSystem.Web.HttpUtility.UrlPathEncode, because I use .Net 4.0
– Olja Muravjova
Nov 15 at 10:55
Thank you, that worked for me. I used
System.Web.HttpUtility.UrlPathEncode, because I use .Net 4.0– Olja Muravjova
Nov 15 at 10:55
Thank you, that worked for me. I used
System.Web.HttpUtility.UrlPathEncode, because I use .Net 4.0– Olja Muravjova
Nov 15 at 10:55
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264518%2funicode-symbols-in-itextsharp-relative-link%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you have that correct font installed on the machine performing the pdf conversion? It sounds like you are missing the needed font.
– Ross Bush
Nov 12 at 14:49
@RossBush I don't understand what do you mean by font installed? These kind of paths are supported in file managers on my computer
– Olja Muravjova
Nov 12 at 15:03
Some fonts like WingDings2 may or may not be installed on the server that is rendering the text. If there is a missing font you will oftentimes see odd squares or other anomalies. What OS are you using to render the PDF?
– Ross Bush
Nov 12 at 17:10
1
@RossBush I used Arial there, however, this font is used to write "text" parameter in pdf and there is no problem with that, the problem is with the link "behind" this text
– Olja Muravjova
Nov 12 at 21:44
1
I am sorry Ross, but you are on a wild goose chase. The font has nothing to do with it. I am more thinking along the lines of the pdf specification being difficult about non-ascii characters in link destinations. I don't know, I'd have to look it up in the pdf reference we have at the office and I am sure that my colleagues wouldn't even have to look it up, but I am quite convinced that a link destination does not have a font.
– Amedee Van Gasse
Nov 13 at 5:33