+- LDraw.org Discussion Forums (https://forums.ldraw.org)
+-- Forum: LDraw Programs (https://forums.ldraw.org/forum-7.html)
+--- Forum: Parts Author Tools (https://forums.ldraw.org/forum-24.html)
+--- Thread: DATHeader 3.0.14.0 - just released (/thread-11694.html)
DATHeader 3.0.14.0 - just released - Michael Heidemann - 2014-01-05
Based on the items below I updated DATHeader today.
You can download as usual from DATHeader homepage.
Please leave your comments to this version as answer to this post - thanks.
I like to sum up here my and hopefully your ideas for improvements of DATHeader. Or, if you say your ideas are not good please also leave a comment. The result should be to improve DATHeader for better work.
1)
Based on the current origin of this part (http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/x582.dat) I think it might be worth to check for the origin to be inside the bounding box. If not give a warning. (Already coded in my develop version).
2)
Based on the current comment on this part (http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/u9292.dat) I think it might be worth to check from the end of the file to the first occurence of a real line for only line breaks and delete those empty lines.
Edit:
DATHeader write only one CR_LF after the last line with content if it is saved. So it is only necessary to detect those unnecessary lines and present the result to the user.
Edit:
Check for those empty lines is now also implemented (Already coded in my develop version).
3)
Based on the current comments on this part (http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/47326c.dat) further documented in the thread http://forums.ldraw.org/showthread.php?tid=11690&pid=11690#pid11690 I think it might be worth to implement a basic language check for at least some common wrongly used words like "color vs. colour", "gray vs. grey". The words to check should be in a separate file, so we can easily extend the list of words. (Already coded in my develop version).
Edit:
I did not know that it is sooo different: http://www.statsci.org/smyth/ozus.html. There are still more pages about this issue so maybe we need a complete dictionary in australian english that I should use in DATHeader.
4)
While working on parts that should use pattern from another part it found it anoying to seach for the data of the pattern that should be integrated into the part. So I added a infobox where the dimensions of the bounding box and the center of the bounding box is noticed, so I only need to open this file in DATHeader and have the values that i need to calculate the position and the zoomlevel. (Already coded in my develop version).
Re: DATHeader - ideas for future releases - Philippe Hurbain - 2014-01-06
Just as a reminder, issue a warning on save if file is not tagged as "Unofficial"...
Re: DATHeader - ideas for future releases - Max Martin Richter - 2014-01-06
In my eyes this was done in the latest version?!
/Max
Re: DATHeader - ideas for future releases - Magnus Forsberg - 2014-01-06
Comment on 2.)
Are you saying that all empty lines at the end of the file should be removed?
I consider it to be good practice to end with a CR/LF.
Please, leave one empty line at the end, but help us remove any extra lines.
Re: DATHeader - ideas for future releases - Philippe Hurbain - 2014-01-06
Oops, I didn't realized that Mike already implemented this suggestion... Thanks for the tip
Re: DATHeader - ideas for future releases - Michael Heidemann - 2014-01-06
It should of course be coded to our standard:
Quote:Line Termination
All lines in the file must use the standard DOS/Windows line termination of(carriage return/line feed). The file is permitted (but not required) to end with a.
Re: DATHeader - ideas for future releases - Michael Heidemann - 2014-01-11
I just finished implementing item 1).
As the calculation of the bounding box will take a while this check should maybe be done only if the user like to have this checked. Often there is no problem and therefore this check will only enlarge the time for the complete file check.
I can make this check based on the preferenced settings of the user, like the t-junction check.
I like to hear some words from the user please.
Thanks for your feedback.
I could not wait
- so I made it mandantory. As standard this check is disabled.
Re: DATHeader - ideas for future releases - Tim Gould - 2014-01-11
Michael Heidemann Wrote:3)
Based on the current comments on this part (http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/47326c.dat) further documented in the thread http://forums.ldraw.org/showthread.php?tid=11690&pid=11690#pid11690 I think it might be worth to implement a basic language check for at least some common wrongly used words like "color vs. colour", "gray vs. grey". The words to check should be in a separate file, so we can easily extend the list of words. (Already coded in my develop version).
Edit:
I did not know that it is sooo different: http://www.statsci.org/smyth/ozus.html. There are still more pages about this issue so maybe we need a complete dictionary in australian english that I should use in DATHeader.
Note that the article you link to isn't entirely correct. Some of it is "old UK/Aus English" rather than modern Aus English and some of it is the authors preference (e.g. I bet every Australian knows and might use 'fender') and some of it is either regional or wrong (e.g. no-one in my part of Aus would say 'potato crisps'). I do not recommend using that list
Here are some words most likely to appear in LDraw parts and that are likely to be incorrect Aus English:
Quote:color/colour
gray/grey
gas/petrol
mailman/postman
cookie/biscuit
*or/*our [we do use 'or' on a few words too... it's probably worth flagging rather than changing those words]
*ize/*ise [we do use 'ize' on a few words too... it's probably worth flagging rather than changing those words]
There's also words like encyclop[æ/ae/e]dia which I've seen spelled in both the old 'ae' way and with just an 'e'. I'd say leave those to the author.
Tim
Re: DATHeader - ideas for future releases (new release is out) - Michael Heidemann - 2014-01-11
Thanks for your feedback.
I raise a warning in the new (just released) DATHeader if the words: gray, color, center are used in the parts description.
More can be added, at present only in a new build. If necessary it can be done on a list of words that is editable.
But at present I think we have now more check than ever
Edit:
I just came across this project http://nhunspell.sourceforge.net/ and this might do the job. But before i can use this I need a dictionary. Does anybody know where I can get a _good_ dictionary in australian english?
Re: DATHeader - ideas for future releases (new release is out) - Tim Gould - 2014-01-12
Excellent
Just for a warning a dictionary isn't sufficient e.g. we have the word 'gas' but we don't use it for a 'petrol station attendent'
That's why I think a fan-made list is best. We can put words and phrases that are most likely to cause problems in the context. It does not need to be comprehensive, just enough to catch obvious words.
Tim
DATHeader 3.0.16.0 - bugfix version - Michael Heidemann - 2014-05-26
Based on the bug report here (http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/s/32474s01.dat) I have uploaded a bugfix version.
Re: DATHeader 3.0.16.0 - bugfix version - Magnus Forsberg - 2014-06-02
I was going to ask: How do I turn off "Rectifier as post processor"?
But then I found a tick box under "External Application". Why there?
Re: DATHeader 3.0.16.0 - bugfix version - Michael Heidemann - 2014-06-05
Because rectifier is an external application and you have to set the path for it to work, so the postprocess can only start if you have specified that path.
If you do not have the path for rectifier specified there, rectifier was never a postprocess