Am 09.01.2014 14:49, schrieb Jonas Maebe:
On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
On 08/01/2014 17:17, Jonas Maebe wrote:
The codepage names used by the codepage directive are (unfortunately, I
guess) unrelated to the code page numbers:
http://www.freepascal.org/docs-html/prog/pr
On 09/01/2014 15:43, Michael Van Canneyt wrote:
> On Thu, 9 Jan 2014, Reinier Olislagers wrote:
>> On 09/01/2014 15:12, Michael Van Canneyt wrote:
>>> On Thu, 9 Jan 2014, Reinier Olislagers wrote:
On 09/01/2014 14:49, Jonas Maebe wrote:
> On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
On Thu, 9 Jan 2014, Reinier Olislagers wrote:
On 09/01/2014 15:12, Michael Van Canneyt wrote:
On Thu, 9 Jan 2014, Reinier Olislagers wrote:
On 09/01/2014 14:49, Jonas Maebe wrote:
On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
On 08/01/2014 17:17, Jonas Maebe wrote:
I see your point,
On 09/01/2014 15:12, Michael Van Canneyt wrote:
> On Thu, 9 Jan 2014, Reinier Olislagers wrote:
>> On 09/01/2014 14:49, Jonas Maebe wrote:
>>> On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
On 08/01/2014 17:17, Jonas Maebe wrote:
>> I see your point, but I think that people should just re
On Thu, 9 Jan 2014, Reinier Olislagers wrote:
On 09/01/2014 14:49, Jonas Maebe wrote:
On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
On 08/01/2014 17:17, Jonas Maebe wrote:
I think that adding links to the manual pages on the wiki is generally
not a good idea, because the names of thos
On 09/01/2014 14:49, Jonas Maebe wrote:
> On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
>> On 08/01/2014 17:17, Jonas Maebe wrote:
> I think that adding links to the manual pages on the wiki is generally
> not a good idea, because the names of those pages change with every FPC
> release. The
On 08 Jan 2014, at 19:37, Reinier Olislagers wrote:
On 08/01/2014 17:17, Jonas Maebe wrote:
The codepage names used by the codepage directive are
(unfortunately, I
guess) unrelated to the code page numbers:
http://www.freepascal.org/docs-html/prog/progsu88.html
They are the names of indiv
On 08/01/2014 17:17, Jonas Maebe wrote:
>
> On 08 Jan 2014, at 15:58, Reinier Olislagers wrote:
>
>> I'm trying to avoid ambiguity for an UTF8 (without BOM) encoded file and
>> tried this:
>> {$ifdef fpc}
>> //Explicitly specify this is an UTF8 encoded file.
>> //Alternative would be UTF8 with
On 08 Jan 2014, at 15:58, Reinier Olislagers wrote:
I'm trying to avoid ambiguity for an UTF8 (without BOM) encoded file
and
tried this:
{$ifdef fpc}
//Explicitly specify this is an UTF8 encoded file.
//Alternative would be UTF8 with BOM but writing UTF8 BOM is bad
practice.
//See
http:
First, thanks to all involved in documenting the existing FPC trunk
Unicode situation on the wiki. Exactly the kind of docs I was looking for!
I'm trying to avoid ambiguity for an UTF8 (without BOM) encoded file and
tried this:
{$ifdef fpc}
//Explicitly specify this is an UTF8 encoded file.
//
10 matches
Mail list logo
