Read unicaode symbols from word in labview

[ramesh_ni]

Hi everyone,

I am trying to read the bookmarked date from MS word file. But symbols like < and ohm symbol are not read properly by labview. these are displayed as ? in the labview string fields. 

I have attached teh code and a sample doc. Kindly look into it.

When I browsed through forums, I am suspecting that it is ascii and unicode encodingh issue. 

Kindly reply. 

Thanks in advance for all the replies.

[crossrulz]

1. Go give this idea a kudo: Support Unicode

2. See this article: LabVIEW Unicode Programming Tools

[billko]

This is NOT a unicode problem.  It is a problem with the font you are using.

[Bob_Schor]

---

@billko wrote:

This is NOT a unicode problem.  It is a problem with the font you are using.

---

Bill,

     Can you please explain what you mean?  When I looked at the Word Document, it seemed to show an Ohm Sign, Unicode 2126, and Less-than-or-equal-to, Unicode 2264.  When you refer to "the font", is that the Font property of the Indicator being used?  Should that be set in some special way?  Does one have to "worry" about specifying the Encoding Scheme?  Should one read U16 and do manipulations?

     Needless to say, I'm very happy that I've not (yet) had to deal with this directly!  Your graphic expertise would be welcomed (by me, at any rate).

Bob Schor

[billko]

---

@Bob_Schor wrote:

---

@billko wrote:

This is NOT a unicode problem.  It is a problem with the font you are using.

---

Bill,

     Can you please explain what you mean?  When I looked at the Word Document, it seemed to show an Ohm Sign, Unicode 2126, and Less-than-or-equal-to, Unicode 2264.  When you refer to "the font", is that the Font property of the Indicator being used?  Should that be set in some special way?  Does one have to "worry" about specifying the Encoding Scheme?  Should one read U16 and do manipulations?

     Needless to say, I'm very happy that I've not (yet) had to deal with this directly!  Your graphic expertise would be welcomed (by me, at any rate).

Bob Schor

---

Well Bob, I'll explain it like this:

I can't explain it.  I was thinking about how I used to solve that in the old days, by choosing a font that was able to display those characters, but when you made me think more closely about it... I realized it was a Unicode font that I was switching to.  So in other words, you are correct, and I am not.  That's how I explain it.