Re: [open-cobol-list] OpenCOBOL 2.0

[Brian Tiffin]

It can take a few google translates, but the source code from a team
in Japan, OpenCOBOL 1.3J is utf-8 ready, or SJIS.  Might have some
hints.

http://www.osscons.jp/osscobol/download/

And thanks for the heads up on the Makefile inputs.

Cheers,
Brian


On 10/25/13, Patrick <address@hidden> wrote:
> On 10/25/2013 06:53 PM, Kevin Monceaux wrote:
>> Fellow COBOL Fans,
>>
>> Thanks to a recent post on the list I just noticed OpenCOBOL 2.0 is
>> available for download.  It took me a while to find it.  1.1 is still the
>> lastest listed on the OpenCOBOL web site.
>>
>> What's new in 2.0?  The last entry in the ChangeLog file in the source
>> tarball is from June of 2010.
>>
>> Can 2.0 handle wide characters?  I see it links against ncursesw now
>> instead
>> of ncurses, and I see a few spots in libcob/screenio.c where setlocale
>> would
>> be called, but those spots are wrapped with #if 0 ...  #endif.  My C
>> skills
>> are at the novice level at best.  Does the #if 0 ...  #endif essentially
>> comment out the code in between?  I tried compiling a program with 2.0
>> and
>> couldn't enter wide characters.  I then tried patching libcob/screenio.c
>> to
>> include a call to setlocale that would get executed, as I've done with
>> OpenCOBOL 1.1 in the past, but still couldn't enter wide characters.
>>
>> Is there a way to position the cursor when using the SCREEN SECTION in
>> 2.0?
>> That's one feature I've often wished was available in 1.1.
>>
>> Is there a way to customise the promptchar without patching
>> libcob/screenio.c?  I run programs via rxvt-unicode locally and/or
>> remotely
>> via PuTTY.  Both are capable of displaying underlined text.  I underline
>> fields with the UNDERLINE keyword in the SCREEN SECTION.  I don't like
>> having fields filled with underscores.
>>
>> I noticed one build problem when I was creating an ArchLinux package for
>> OpenCOBOL 2.0.  There's a part in the libcob Makefile that removes
>> several
>> files from $(includedir)/libcob/.  It ignores $(DESTDIR).  By patching
>> the
>> Makefile.{am,in} files and adding $(DESTDIR) to all the
>> rm $(includedir)/libcob/... commands I was able to build an ArchLinux
>> package.
>>
>>
>>
> Hi Kevin
>
> I installed 2.0. I was having some trouble debugging a program so I
> reinstalled 1.1 . 2.0 was not the problem but the point is I don't have
> it installed right now.
>
> The first thing I did when I installed 2.0 was to test for unicode
> support in the screen section. It seemed to work fine.
>
> I think I used the N picture clause rather then X. If you didn't maybe
> you could try this.
>
> -Patrick
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> open-cobol-list mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/open-cobol-list
>