Several export problems

395 views
Skip to first unread message

Mihajlo Cvetanović

unread,
Dec 11, 2013, 1:13:08 PM12/11/13
to zeta-resou...@googlegroups.com
I have a fairly complex C# VS2008 WinForms project with en-US as neutral language, and five more languages. Resources for those five languages I created using ZRE + Visual Studio where ZRE can't manage. I use ZRE 2.2.0.28. I want to use export so that I can employ translators for new languages, but some exporting features of ZRE are simply not working for me. It took me time to write this, so please read it.

1. When I create new ZRE project and use option "Automatically add file groups from Visual Studio solution" to open a .sln file only one file group is added (Resources(.*).resx). Actual C# project contains more, notably MainForm(.*).resx, but also other. ZRE project file (.zreproj) contains only this one file group, with uniqueID="00000000-0000-0000-0000-000000000000" XML attributes in seven places. Where are the other file groups?

2. I can walkaround the failure in case (1) by manually adding all the file groups. If I add one more file group (like MainForm(.*).resx) with command "Add existing file group to project" the group will be added, though with yellow icon instead of green.

3. If I start from project in case (1) and try "Export to Microsoft Excel" command with all the options reset to default I get one .xls file with texts on all six languages. One file group is better then nothing, I guess.

4. If I try case (3), but enable "Export file group column" checkbox I get this error: "Value was either too large or too small for an Int32.Couldn't store <10179398425> in Group Column.  Expected type is Int32.". This means that I cannot use single sheet in single file for all my file groups, because then I cannot distinguish between them. Why is this happening?

5. If I try case (3), but with selected option "Export each file group into a separate work sheet" I get one .xls file with sheet name "D_#Path#to#my#project#31char...". So far so good, but I had only one file group.

6. If I try case (2) (two file groups), but with selected option "Export each file group into a separate work sheet" I get this error: "A DataTable named 'D_#Path#to#my#project#31char...' already belongs to this DataSet.". It's because two data sheets cannot have the same name. It's an error in sheet naming algorithm.

7. I can workaround the failure in case (6) by moving the whole project to the disk root (or better yet, using SUBST in command prompt), so that paths become very short and unique when truncated to 28 characters.

7b. When I add all the file groups manually and export to single .xls file with one worksheet per file group, some file groups will not be exported, and their worksheets will not exist. Why is this happening?

8. If I try case (2), but with selected option "Export each file group into a separate Excel document" I get two Excel files, but one of them (for MainForm) displays this error in Excel 2010: "Excel found unreadable content in 'MyPoject-MainForm.resx.xls'. Do you want to recover the contents of this workbook? If you trust the source of this workbook, click Yes." I don't see the contents even if I click Yes. Why is this happening? The contents is visible if I open the file in Notepad++.

9. If I start from project in case (1) and try "Automatically add multiple file groups to project" only one new group will be added (and there are plenty of them remaining), and ironically it's not really a group but one .resx file that is not supposed to be localized anyway. uniqueID is again set to all zeros in two places for this file group. Icons for both file groups are green, and if I manually add any other file group it would have a yellow icon. Where are the other file groups?

Failure of cases (7b) and (8) are a showstopper for me. I can't send Excel documents to a translator because I cannot create them all. Only some file groups can be exported.

Ken Kick

unread,
Jun 19, 2014, 2:19:07 PM6/19/14
to zeta-resou...@googlegroups.com

Mihajlo Cvetanović

unread,
Jun 19, 2014, 6:25:59 PM6/19/14
to zeta-resou...@googlegroups.com
Nice. Maybe we should fork it and more than just fix some bits?

Uwe Keim

unread,
Jun 20, 2014, 1:41:57 AM6/20/14
to zeta-resou...@googlegroups.com
I've intentionally published my code to Github in order to enable easy forking/development by others.

Ken Kick

unread,
Jun 25, 2014, 10:55:01 AM6/25/14
to zeta-resou...@googlegroups.com
Critical Import Fix and Export Fix FORKED

:)
Reply all
Reply to author
Forward
0 new messages