Loading...
 
Multi-Language Add-In for Visual Studio

Multi-Language Add-In for Visual Studio


Wish list

Wish list
- Please restore Add-in window docking position from previus work-session (currently - always floated)
- Dream about one useful option - "Check for software updates when starting" :-)
- Export to Excel wizard: option "Export only untranslated strings"

Germany

I though that the Visual Studio did remember where the window was docked! I will have to test this again.

I mostly start the Add-In in the debugger, and in this case the window also starts as a floating window. I was fairly sure that this was an effect in the debugger, which it may or may not be, so I have usually ignored it.

I have started implementing an option to export only untranslated strings to Excel. It should be ready in the next day or two.

What do you think about exporting strings which have been changed?

The Add-In shows the text in the original language in red, if it does not match the text in the project. I thought about exporting these strings as well, but this may be too naive. If you simply update the text in the original language, then it would no longer be exported, even if the other languages had not been updated. Ideally, it would require a dirty-flag for every single translation, set to dirty when the original text was modified, and reset when the translation was edited. That might be a brilliant feature, or completely over the top.

Phil

> I though that the Visual Studio did remember where the window was docked!
Me too :-(

> I have started implementing an option to export only untranslated strings to Excel. It should be ready in the next day or two.

Great! It will be very useful options for project recently updated

> What do you think about exporting strings which have been changed?
I think that it will be second option.

Export wizard options

Export all strings
* Export only
x untraslated
x changed

>
> The Add-In shows the text in the original language in red, if it does not match the text in the project. I thought about exporting these strings as well, but this may be too naive. If you simply update the text in the original language, then it would no longer be exported, even if the other languages had not been updated. Ideally, it would require a dirty-flag for every single translation, set to dirty when the original text was modified, and reset when the translation was edited. That might be a brilliant feature, or completely over the top.
Agree

Germany

I have now uploaded a new version (4.60.0024) with the option to export only untranslated strings.

At the same time, I have enabled a new Excel export/import which I developed recently. I will write something about this in a separate posting. (The previous export is still available.)

Phil

> I have now uploaded a new version (4.60.0024) with the option to export only untranslated strings.
Thank you!

One more moment.

My solution contains several projects (website + few class libraries).

Hope it is good idea - allow export strings (all or unlocalized) from all projects of solution in single Excel file.

Right now when i need send files to translators i make multiple exports every time.


> At the same time, I have enabled a new Excel export/import which I developed recently. I will write something about this in a separate posting. (The previous export is still available.)
>

Too many menu items in dropdown list at button with Excel logo :-)
I think must be only 2 items: export, import

But export wizard can allow select user export type from combobox.

Import wizard can detect type of file to import without user, automatically.