Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #7201

Re: ReportPro 3.9e RTF style problem

From "Willie Moore" <williem@wmconsulting.com>
Newsgroups comp.lang.clipper.visual-objects
Subject Re: ReportPro 3.9e RTF style problem
Date 2014-09-11 10:36 -0500
Organization Aioe.org NNTP Server
Message-ID <lusfhd$vlr$1@speranza.aioe.org> (permalink)
References <lu4l19$jcp$1@speranza.aioe.org> <lu78al$lr0$1@speranza.aioe.org> <lu7ln1$p7r$1@speranza.aioe.org> <lupjgp$spn$1@speranza.aioe.org> <lupvug$10c$1@speranza.aioe.org>

Show all headers | View raw


Jamal,

Yes RP3 for Vulcan does have ActiveX. I have not personally tried it from VO 
but I will set up some time over the weekend to try it.

Regards,
Willie
Vulcan VIP

"Jamal"  wrote in message news:lupvug$10c$1@speranza.aioe.org...

Willie,

Does the ReportPro 3 .NET edition have an Activex control?

If so, may be it can be used in VO an overcome  the unicode issue.

Jamal

"Willie Moore"  wrote in message news:lupjgp$spn$1@speranza.aioe.org...

Jamal,

The Vulcan version of RP3 supports unicode. But the VO version is all built
on ansi so it will never been in unicode. As for encoding, you can do things
like this:

Encoding ANSI = Encoding.GetEncoding(1252);

byte[] ansiBytes = ANSI.GetBytes(str);
byte[] utf8Bytes = Encoding.Convert(ANSI, Encoding.UTF8, ansiBytes);

String utf8String = Encoding.UTF8.GetString(utf8Bytes);

By changing the defaults, you can convert the text in either direction.

Regards,
Willie
Vulcan VIP

"Jamal"  wrote in message news:lu7ln1$p7r$1@speranza.aioe.org...

Willie,

>>

You might try a converter to save your rich text as ansi. <<

Any hints on how this is done either in .NET or VO.  My web search did not
yield any useful results.

Since you have been doing maintenance on RP, is there a possibility that you
can update RP to handle unicode?

Jamal


"Willie Moore"  wrote in message news:lu78al$lr0$1@speranza.aioe.org...

Jamal,

If it is coming from a dotNet RichTextBox it will be using unicode which I
do not think RP3 will accept. You might try a converter to save your rich
text as ansi.

Regards,
Willie
Vulcan VIP

"Jamal"  wrote in message news:lu4l19$jcp$1@speranza.aioe.org...

It seems ReportPro 3.9e does not respect the styles of in an RTF file for
example Bold and Underline, Bullets, etc. The RTF files are created in using
.NET RichTextBox control which might be creating this incompatibility.

Can anyone tell me what RTF specification ReportPro uses and how I overcome
the issue in my VO app or if there is a fix?

Thanks,
Jamal 

Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

ReportPro 3.9e RTF style problem "Jamal" <someone@example.com> - 2014-09-02 10:42 -0400
  Re: ReportPro 3.9e RTF style problem "Willie Moore" <williem@wmconsulting.com> - 2014-09-03 09:24 -0500
    Re: ReportPro 3.9e RTF style problem "Jamal" <someone@example.com> - 2014-09-03 14:13 -0400
      Re: ReportPro 3.9e RTF style problem "Willie Moore" <williem@wmconsulting.com> - 2014-09-10 08:25 -0500
        Re: ReportPro 3.9e RTF style problem "Jamal" <someone@example.com> - 2014-09-10 12:51 -0400
        Re: ReportPro 3.9e RTF style problem "Jamal" <someone@example.com> - 2014-09-10 12:58 -0400
          Re: ReportPro 3.9e RTF style problem "Willie Moore" <williem@wmconsulting.com> - 2014-09-11 10:36 -0500
            Re: ReportPro 3.9e RTF style problem "Jamal" <someone@example.com> - 2014-09-19 12:37 -0400
              Re: ReportPro 3.9e RTF style problem "Willie Moore" <williem@wmconsulting.com> - 2014-09-20 11:39 -0500
                Re: ReportPro 3.9e RTF style problem "Jamal" <someone@example.com> - 2014-09-20 13:14 -0400

csiph-web