2009-11-26 03:09 UTC
{2}
I have decided to extract pieces from one of the project that i currently developing,
assemble this Demo, and share, before my project gone to be more application specific,
and include more resources and connections.
Concept is that (if well prepared) OpenDCL can employ external/editable language (.lng) files
to fill "translatable" controls.
In this demo, initialization of proper .lng file is accomplished with a single function call immediately
after dcl_Project_Load is called.
-------
Plot 1.
Lng file (actually support for lng files) can be included in Project, if this function is putted.
Language files can be distributed with project to end users, and they can create (translate)
project interface to match their needs, and maybe spread around this .lng files, or upload
back to author, or Author can expose option inside application for changing languages.
Plot 2.
Lng files can be used by author only in developing stage for easier translation.
- Demo include function for creation base (starting) .lng file from the .odcl file. (C:LNGEN)
After translation of extracted .lng file, author can merge .lng file data with .odcl file data,
and save as new .odcl file. Function (c:lng2odcl).
-------
This demo is combined (rich) with some of the functions that i pull out from my library
so maybe this also can be interested.
Put all files (9) in ACAD support file and appload "LNGF-DEMO.LSP".
Enjoy
I have decided to extract pieces from one of the project that i currently developing,
assemble this Demo, and share, before my project gone to be more application specific,
and include more resources and connections.
Concept is that (if well prepared) OpenDCL can employ external/editable language (.lng) files
to fill "translatable" controls.
In this demo, initialization of proper .lng file is accomplished with a single function call immediately
after dcl_Project_Load is called.
-------
Plot 1.
Lng file (actually support for lng files) can be included in Project, if this function is putted.
Language files can be distributed with project to end users, and they can create (translate)
project interface to match their needs, and maybe spread around this .lng files, or upload
back to author, or Author can expose option inside application for changing languages.
Plot 2.
Lng files can be used by author only in developing stage for easier translation.
- Demo include function for creation base (starting) .lng file from the .odcl file. (C:LNGEN)
After translation of extracted .lng file, author can merge .lng file data with .odcl file data,
and save as new .odcl file. Function (c:lng2odcl).
-------
This demo is combined (rich) with some of the functions that i pull out from my library
so maybe this also can be interested.
Put all files (9) in ACAD support file and appload "LNGF-DEMO.LSP".
Enjoy