Hi Mateusz,
Folks,
I'm trying to update GDAL's copy of json-c library.
The task is not trivial, due to the fact GDAL has applied
some sort of improvements to json-c, and also due to
significant changes to how json-c works, UTF-8 support, etc.
Just curious about the changes in UTF-8 support
Selon Jukka Rahkonen jukka.rahko...@mmmtike.fi:
Ivan Lucena ivan.lucena at princeton-ma.us writes:
Hi there,
Is there any trick to avoid creating field names with reserved words? For
example, a DBF from a shapefile can
have field names like long and other formats may not like it.
Even Rouault wrote:
Selon Jukka Rahkonen jukka.rahko...@mmmtike.fi:
Ivan Lucena ivan.lucena at princeton-ma.us writes:
Hi there,
Is there any trick to avoid creating field names with reserved words? For
example, a DBF from a shapefile can
have field names like long and other formats
On 15 July 2012 11:01, Even Rouault even.roua...@mines-paris.org wrote:
I'm trying to update GDAL's copy of json-c library.
The task is not trivial, due to the fact GDAL has applied
some sort of improvements to json-c, and also due to
significant changes to how json-c works, UTF-8 support,
Hi Dmitry,
I tried to do that, but still got errors:
/Error 36 error LNK2019: unresolved external symbol _CSLPartialFindString
referenced in function public: int __thiscall
CPLStringList::PartialFindString(char const *)const
(?PartialFindString@CPLStringList@@QBEHPBD@Z)
