News:

Download Pelles C here: http://www.pellesc.se

Main Menu

Recent posts

#11
Bug reports / Re: IDE Reload. Eroteme Replac...
Last post by John Z - January 16, 2026, 11:06:59 PM
Hi Robert,

This is not really a bug.  It maybe a minor inconvenience but here is the situation as I understand it.

Pelle C was originally ASCII/ANSI for all source files.
Pelle C converted to having UTF-8 the default for all source files. 

It also supports UTF-16 for source files. When you create a new source file within the IDE it is automatically UTF-8.  You will see that the source file tab also shows UTF-8 (or UTF-16).  If it shows nothing but the name the source file is at best ASCII/ANSI.  When using 'OLD' source code or creating the source code file outside of Pelle C with a plain text editor it will be ASCII/ANSI

Now the critical part is that the editor now works in UTF-8 by default always.  This allows the editor to enter UTF-8 in the source code page, but since that page is not identified as UTF-8 when reloaded it will fail to display as expected.

So the Export64 program for example does not show UTF-8 in the tab so it is still ASCII/ANSI, even though the editor can make the 'display' show the character.

Using any editor that supports UTF-8 a source file can be created or just resaved saved with the encoding set to UTF-8.

I use TextPad for example to resave Export.c to Export_UTF8.c and if you add it to the Export64 program you will see the source tab shows the encoding.  If you run your test on this file it should 'pass' reloading -

Hope this was at least a little bit clear -

John Z

The other method is to create a blank source file in the IDE then paste in the old source code. When saved it will be UTF-8



#12
Beginner questions / Re: Small C Programs to Learn ...
Last post by Vortex - January 16, 2026, 10:01:48 PM
Hi jos,

In the manual supplied with Pelles C ( \PellesC\Bin\Help\help0009.chm ) search for this : Predefined preprocessor symbols (POCC)
#13
Add-ins / Re: Export C source as HTML or...
Last post by Robert - January 16, 2026, 06:54:57 PM
Quote from: TimoVJL on January 16, 2026, 06:34:08 PMzlib 1.3.1 project with missing header file, that dependecies forgot.

zlib 1.3.1 Release Notes

Thanks Timo  8)
#14
Bug reports / IDE Reload. Eroteme Replaces U...
Last post by Robert - January 16, 2026, 06:48:39 PM

When the poide.exe IDE is shut down and restarted, the UTF-8 in this code


#include <stdio.h>

/* entry point */
int main(void)
{
  printf("Hello, world!\n");
  printf("Салом Ҷаҳон!\n");
 
  return 0;
}


is reloaded to the poide.exe IDE, with question marks replacing the UTF-8, as


#include <stdio.h>

/* entry point */
int main(void)
{
  printf("Hello, world!\n");
  printf("????? ?????!!\n");
 
  return 0;
}


Tofu
https://fonts.google.com/knowledge/glossary/tofu

Eroteme
https://en.wiktionary.org/wiki/eroteme
https://en.wikipedia.org/wiki/Question_mark
#15
Add-ins / Re: Export C source as HTML or...
Last post by TimoVJL - January 16, 2026, 06:34:08 PM
zlib 1.3.1 project with missing header file, that dependecies forgot.

zlib 1.3.1 Release Notes
#16
Add-ins / Re: Export C source as HTML or...
Last post by Robert - January 16, 2026, 06:30:52 PM
Quote from: John Z on January 16, 2026, 11:45:34 AMHi Robert,

My apologizes, I didn't check that the project zip was complete.  I updated the post with a project zip that includes the libs. 

I'll look further into it (UTF-8) with the link you provided.

Hopefully good memories for you :)

John Z

Hi John Z:

Thanks, the zlib64 is good. Export is as expected with the limitations you have mentioned regarding UTF-8.

There is a separate but maybe connected problem with Pelles poide.exe IDE.

This code


#include <stdio.h>

/* entry point */
int main(void)
{
  printf("Hello, world!\n");
 
  return 0;
}


amended by adding a print in Tajik UTF-8


#include <stdio.h>

/* entry point */
int main(void)
{
  printf("Hello, world!\n");
  printf("Салом Ҷаҳон!\n");
 
  return 0;
}


is reloaded to the poide.exe IDE as


#include <stdio.h>

/* entry point */
int main(void)
{
  printf("Hello, world!\n");
  printf("????? ?????!!\n");
 
  return 0;
}


when the IDE is shut down and restarted.
#17
Beginner questions / Re: Small C Programs to Learn ...
Last post by jos - January 16, 2026, 04:06:59 PM
Many thanks again,
Now it works! I'm only using PelleC at the moment, is there a list of all the must-"haves" or not use when using __POCC__? Is there any site to read?
#18
Beginner questions / Re: Read PDF text with PDFio
Last post by TimoVJL - January 16, 2026, 01:11:55 PM
Project file for pdf2text, using pdfio.dll
#19
Beginner questions / Re: Small C Programs to Learn ...
Last post by TimoVJL - January 16, 2026, 01:08:33 PM
put
#ifndef __POCC__
typedef __int64 ssize_t;        // POSIX type not present on Windows... @private@
#endif
or#ifndef __POCC__
typedef size_t ssize_t;
#endif
it should be in <sys/types.h> without any ifdefs

before headers to pdf2text.c
of mofify pdfio.h and put it there
also compile with -Go Define compability names
#20
Beginner questions / Re: Small C Programs to Learn ...
Last post by jos - January 16, 2026, 12:47:25 PM
Thanks, have gone through theForger, Windows API etc. Scan the net and try to read and understand code I find in C.

I feel like I'm making progress (slowly) when I start from scratch. But trying to use routines or other general programs I get so many errors and warnings! I guess my knowledge of pragma etc. limits me. But it will come eventually...

I have new problems with PDFio, trying to test and compile a file in the library example: pdf2text. (The example I got earlier works just fine?)

PS. have upgraded to Pellesc 13.00.9