Wings 1.1.12 has been released - WINGS 3D - Wings - Wings3D - Official Development Forum - Message Board Yuku

RSS
Email

0 Kudos

<< Previous Topic Next Topic >>

Wings 1.1.12 has been released

Author	Comment
bjorng	Wings 1.1.12 has been released	Lead	[-]
(08/28/09 23:35:34) Reply Quote More My Recent Posts	Tags : None Time for a new bug fix release. The changes to Select\|Edge Loop to allow it to select edges around holes did not make it for this release, because we found various issues. I hope we have sorted out the issues in time for the next release. Enjoy! /Björn - For developers: In the source distribution, there is a new text file CodingGuidelines containing coding guidelinings for Erlang programming in general and Wings programming in particular. (Thanks to optigon, deerwood, and scorpius for comments on the first draft.) [bjorng] - For developers: Basic multiple column support has been implemented in the table widget in wings_ask. [bjorng] - Doing a vertex bevel on an object with both vertex attributes and a virtual mirror would cause a crash. (Thanks to ycarry.) [bjorng] - Exporting objects with holes and more than one material would cause a crash. (Thanks to ycarry and TulipVorlax.) [bjorng] - Exporting a scene with area lights with the Yafray exporter would cause a crash. (Thanks to spacemanspiff7.) [bjorng]
TulipVorlax		#1	[-]
(08/29/09 10:54:17) Reply Quote More My Recent Posts	Hi, Thanks. Did any strings changed in the english lang ? Download link not yet on main page : http://sourceforge.net/projects/wings/files/wings/1.1.12/wings-1.1.12.exe/download
GetaVe		#2	[-]
(08/31/09 17:08:38) Reply Quote More My Recent Posts	great job!
deerwood	Re: Did any strings changed in the english lang ?	#3	[-]
(08/31/09 22:36:19) Reply Quote More My Recent Posts	Hi TulipVorlax, a simple way to figure out translation work to do is to search all the _fr.lang files for comments (starting with '%%'). Not by hand, naturally, but by some program able to search many files recursively, see below. Background: when Wings is built, the build process generates* all the _en.lang files from the .erl sources (the translatable strings are specially marked in the sources, by ?__(<some_number>, "string to translate") or ?STR(<some_atom>, <some_number>, "string to translate") ). Then every existing not english XYZ_??.lang file is checked against the just generated XYZ_en.lang file, and if there is a structure difference, the XYZ_??.lang gets appended with comments about recommended actions / hints. Might be, there are other ways to check (there even might be a usable GUI program to do the check) but assuming you are either on Unix, or on Mac OSX and know how to start the terminal, or on Win with cygwin installed you can do the following in the shell/terminal: cd <to_your_wings_install>/lib/wings<version> find . -name '*_fr.lang' \| xargs grep '%%' \| grep -v mode:erlang This will give you a list of all filenames/lines in the french lang files needing some attention. Excerpt for 1.1.12: ... ./plugins/commands/wpc_tweak_fr.lang:%% The following strings have no translation. ./plugins/commands/wpc_tweak_fr.lang:%% ./plugins/commands/wpc_weld_fr.lang:%% ./plugins/commands/wpc_weld_fr.lang:%% The following strings have no translation. ./plugins/commands/wpc_weld_fr.lang:%% ./plugins/default/wp9_dialogs_fr.lang:%% ./plugins/default/wp9_dialogs_fr.lang:%% The following strings have no translation. ./plugins/default/wp9_dialogs_fr.lang:%% ./plugins/import_export/wpc_yafray_fr.lang:%% [wpc_yafray,help,1] is not used ./plugins/import_export/wpc_yafray_fr.lang:%% [wpc_yafray,help,2] is not used ./plugins/import_export/wpc_yafray_fr.lang:%% [wpc_yafray,help,3] is not used ./plugins/import_export/wpc_yafray_fr.lang:%% [wpc_yafray,help,4] is not used ./plugins/import_export/wpc_yafray_fr.lang:%% [wpc_yafray,help,5] is not used ./plugins/import_export/wpc_yafray_fr.lang:%% [wpc_yafray,props,3] is not used ./plugins/import_export/wpc_yafray_fr.lang:%% ./plugins/import_export/wpc_yafray_fr.lang:%% The following strings have no translation. ./plugins/import_export/wpc_yafray_fr.lang:%% ./plugins/primitives/wpc_knot_fr.lang:%% [wpc_knot,torus_menu] is not used ./plugins/primitives/wpc_knot_fr.lang:%% ./plugins/primitives/wpc_knot_fr.lang:%% The following strings have no translation. ./plugins/primitives/wpc_knot_fr.lang:%% ./plugins/primitives/wpc_torus_fr.lang:%% [wpc_torus,make_lutorus] is not used ./plugins/primitives/wpc_torus_fr.lang:%% [wpc_torus,make_sptorus] is not used ./plugins/primitives/wpc_torus_fr.lang:%% [wpc_torus,make_uvtorus] is not used ... Note, that I'm unsure, if your translations already made it into 1.1.12! Best regards

<< Previous Topic Next Topic >>