.NET
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
*Tony Tanzillo
StringToCI
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
88 Views, 5 Replies
06-10-2005 02:10 PM
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
*Albert Szilvasy
Re: StringToCI
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-10-2005 10:28 PM in reply to:
*Tony Tanzillo
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo" wrote in message
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo"
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
*Tony Tanzillo
Re: StringToCI
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-11-2005 02:30 AM in reply to:
*Tony Tanzillo
Thanks for the clarification.
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy" wrote in message news:4872379@discussion.autodesk.com...
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo" wrote in message
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy"
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo"
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
*Albert Szilvasy
Re: StringToCI
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-11-2005 10:29 AM in reply to:
*Tony Tanzillo
Well, if you filter for some string valued group codes then those are CIF.
So if you are not using our interop code then you will need to translate
from UTF16 to CIF and vice versa.
albert
"Tony Tanzillo" wrote in message
news:4872431@discussion.autodesk.com...
Thanks for the clarification.
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy" wrote in message
news:4872379@discussion.autodesk.com...
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo" wrote in message
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
So if you are not using our interop code then you will need to translate
from UTF16 to CIF and vice versa.
albert
"Tony Tanzillo"
news:4872431@discussion.autodesk.com...
Thanks for the clarification.
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy"
news:4872379@discussion.autodesk.com...
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo"
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
*Tony Tanzillo
Re: StringToCI
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-11-2005 01:39 PM in reply to:
*Tony Tanzillo
Ok. But how would that translation affect wildcards
a la acutWcMatch() ?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy" wrote in message news:4872510@discussion.autodesk.com...
Well, if you filter for some string valued group codes then those are CIF.
So if you are not using our interop code then you will need to translate
from UTF16 to CIF and vice versa.
albert
"Tony Tanzillo" wrote in message
news:4872431@discussion.autodesk.com...
Thanks for the clarification.
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy" wrote in message
news:4872379@discussion.autodesk.com...
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo" wrote in message
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
a la acutWcMatch() ?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy"
Well, if you filter for some string valued group codes then those are CIF.
So if you are not using our interop code then you will need to translate
from UTF16 to CIF and vice versa.
albert
"Tony Tanzillo"
news:4872431@discussion.autodesk.com...
Thanks for the clarification.
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy"
news:4872379@discussion.autodesk.com...
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo"
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
*Albert Szilvasy
Re: StringToCI
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-11-2005 08:39 PM in reply to:
*Tony Tanzillo
When we convert from UTF16 to the internal string representation then only
the characters that cannot be represented in the current code page are
turned into CIF sequences (the rest are simply represented as code point in
the current code page). So, as long as you use characters from the current
code page you are fine. If not, you are not worse off than the rest of
autocad.
Albert
"Tony Tanzillo" wrote in message
news:4872527@discussion.autodesk.com...
Ok. But how would that translation affect wildcards
a la acutWcMatch() ?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy" wrote in message
news:4872510@discussion.autodesk.com...
Well, if you filter for some string valued group codes then those are CIF.
So if you are not using our interop code then you will need to translate
from UTF16 to CIF and vice versa.
albert
"Tony Tanzillo" wrote in message
news:4872431@discussion.autodesk.com...
Thanks for the clarification.
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy" wrote in message
news:4872379@discussion.autodesk.com...
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo" wrote in message
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
the characters that cannot be represented in the current code page are
turned into CIF sequences (the rest are simply represented as code point in
the current code page). So, as long as you use characters from the current
code page you are fine. If not, you are not worse off than the rest of
autocad.
Albert
"Tony Tanzillo"
news:4872527@discussion.autodesk.com...
Ok. But how would that translation affect wildcards
a la acutWcMatch() ?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy"
news:4872510@discussion.autodesk.com...
Well, if you filter for some string valued group codes then those are CIF.
So if you are not using our interop code then you will need to translate
from UTF16 to CIF and vice versa.
albert
"Tony Tanzillo"
news:4872431@discussion.autodesk.com...
Thanks for the clarification.
A simple question is, if I want to build a resbuf chain
to feed to acedSSGet() as a filter (as opposed to stuffing
it into xdata or an xrecord), does that conversion still
apply, or not?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"Albert Szilvasy"
news:4872379@discussion.autodesk.com...
CIF is the iternal encoding of strings that dwgs use currently. If you work
with the C++ API then you might've seen stuff like U+\1334 or similar. On
the .NET API we use unicode (UTF-16) encoding and this class along with its
counterpart (CIFToString) is used to convert CIF and UTF16. If you use the
.NET API you don't need this. If you write interop code then you need it and
it is in fact public. Look at the mgdinterop.h on the ObjectARX SDK.
Albert
"Tony Tanzillo"
news:4872222@discussion.autodesk.com...
I'm guessing this is doing some kind of code page
conversion, but am not sure.
The real quesiton I have is why isn't it public?
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
