libdfxrw status, write, text codec and other issues.

Hello all,
With the pull from today the status are almost ready.
the read/write are complete, in terms of supported emtities,
for version R14, 2000, 2004, 2007 and 2010.
For version R12 does not write ellipse, dimensions & hatch,
these entities are not supported by R12 and can convert to
unnamed blocks and ellipse to approximate polyline.
Some unsupported entities are added:
RAY, XLINE, 3DFACE (converted as polyline)


About strings:

I added in the library a codec that converts text between
code pages and Unicode, then the interface into the lib
and the program are always in unicode (encoded as UTF-8).
The codec are tested in my suse 64b and in a windows XP 32b
For develop and test I write a simple QT program (attached)
I need people for test in other systems and languages like
chinese, japanese, russian, polish, ucranian, etc. testcp.zip

About versions:

I think the default version must be 2007 (published in 2006)
because the text are in UTF-8 instead of using old 8 bytes
windows code pages.

As usual, are needed testers

Cheers,
Rallaz

I'm using LibreCAD 1.0.2-1.1 as released in the Fedora 16 RPM.

I know how to get source from github and build apps.

I'm having a few problems with the current version of LibreCAD, namely exporting files to ACAD users, losing files with the export feature, etc.  

Judging by some of the dev work done recently, I suspect that these issues have been addressed in the latest code check ins.

I would like to test (a) new version(s) of libreCAD and use it for my daily work.   I'll do lots of backups and I understand the risks of doing this.

Code wise, how should I approach doing this ?

What are the chances that someone would (or does) maintain an unstable repository (in either source or compiled form) and every now and then kick a new "RC" into it ?

Or should I just dive into github and pull the latest source and have at it ?

It would be nice for users like me if there was something a bit less raw than the later.

Either way, I'll contribute my feedback in whatever form is useful.

Thanks

I am bussy and I need at least two weeks afterwards I will build RPM's for
LC2 alpha 4 but if you regularly going to use version 2 the best is that you
take the source code and compile it.

To compile in Fedora the prerequisites are:
LibreCAD source code, of course and
make gcc gcc-c++ glibc-devel boost-devel qt4-devel

and libmuparser2-devel from your distro or from:
http://download.opensuse.org/repositories/home:/Rallaz/Fedora_16/

Build instructions are in:
http://librecad.org/cms/home/from-source/linux.html
and remember in Fedora are qmake-qt4

Thanks !

If you follow my other posts today, you'll see that I got it build and I'm up an running with

Version: master
SCM Revision: 2.0.0alpha4-7-gb396762
Compiled on: Jun 27 2012

Standby for feedback !

I may be interested in helping with the Fedora end of the build process, if there is a need for it.  Let me know.

"and remember in Fedora are qmake-qt4"

Very apt advice !  

I spent the biggest part of my build going what the *&^%^O) is wrong with qmake !  LOL

Success.

I spent yesterday trying to troubleshoot the problem behind why a vendor could not work with my QCAD/LibreCAD 1.2.0-1.1 DXF 2000 and DXF R12 files.   I have also had this problem with previous versions of QCAD.

This morning I built Version: master SCM Revision: 2.0.0alpha4-7-gb396762 on my Fedora 16 box.

I opened the same file that the vendor had issues with using the Alpha build and saved files in R14, 2007, 2004 and 2000 formats.  

I sent all the files to the vendor who uses ACAD and a proprietary DXF/DWG quoting tool.  

Both tools opened all the files and worked with them without any trouble.

I am very happy that LibreCAD solved this problem for me.

Thank you.