WPFLocalizeExtension Work Item Rss Feed

Commented Feature: New Setting: Output missing keys flag. [9291]

edif — Fri, 17 May 2013 09:35:08 GMT

The key name should be displayed, if no resource was found for the chosen language.
This applies only to localized texts
Comments: An extension to this would be to externalize a handler for missing key case, or missing content case. Such a handler could be used to automatically create the key in the external storage that is used initially to provide the key-content resources.

Created Unassigned: Finish CSV provider implementation [9293]

MrCircuit — Thu, 16 May 2013 20:52:34 GMT

Based on Kormyrs contribution.

Created Unassigned: Object of type 'SLLocalizeExtension.Extensions.LocTextExtension' cannot be converted to type 'System.String' [9292]

MrCircuit — Thu, 16 May 2013 20:48:14 GMT

Refer to SLTest

Edited Feature: New Setting: Output missing keys flag. [9291]

MrCircuit — Thu, 16 May 2013 20:39:27 GMT

The key name should be displayed, if no resource was found for the chosen language.
This applies only to localized texts

Created Unassigned: New Setting: Output missing keys flag. [9291]

MrCircuit — Thu, 16 May 2013 20:38:14 GMT

Hello,
Thank you for your answer. But my question was: can we display the key from xaml if the key is not present in Resources.resx or any other language file?

Thanks,
Dan

Closed Issue: Difficulties in Making Work [9289]

MrCircuit — Thu, 16 May 2013 20:30:11 GMT

Good morning,

i´m using your program to translate my app.

I´m, having difficulties to make that work.

Please help.

Baltazar

Commented Issue: Difficulties in Making Work [9289]

baltazar_oliveira — Tue, 14 May 2013 13:25:12 GMT

Good morning,

i´m using your program to translate my app.

I´m, having difficulties to make that work.

Please help.

Baltazar
Comments: I have tried again and it works. Thanks

Commented Issue: VB .NET Assembly with dots [9287]

SlickRick — Fri, 12 Apr 2013 19:10:07 GMT

Hi,

it seems like there is an issue with retrieving localized content when a VB project has some dot '.' in the assembly name. (i.e: Wpf.Application1)

But when I change my assembly to WpfApplication1 (no dot) it works fine.

see the attached project for an example of the problem.

(I hope I used the library in the right way)

More information about my environment:
* Visual Studio 2012 SP1
* Windows 8
* VB.NET Project
* Used WpfLocalizeExtension.2.1.2 (from NUGET)

Also see the related discussion (#431609):
http://wpflocalizeextension.codeplex.com/discussions/431609

Comments: Is it supposed to be fixed in version v2.1.3 ? If so I still have the same problem

Commented Issue: Difficulties in Making Work [9289]

MrCircuit — Tue, 09 Apr 2013 12:06:02 GMT

Good morning,

i´m using your program to translate my app.

I´m, having difficulties to make that work.

Please help.

Baltazar
Comments: You can either have a look in the [Download at WorkItem #9269](https://www.codeplex.com/Download/AttachmentDownload.ashx?ProjectName=wpflocalizeextension&WorkItemId=9269&FileAttachmentId=653202) or [Source code & tests download](https://wpflocalizeextension.codeplex.com/downloads/get/652468)

Commented Issue: Difficulties in Making Work [9289]

baltazar_oliveira — Tue, 09 Apr 2013 10:55:27 GMT

Good morning,

i´m using your program to translate my app.

I´m, having difficulties to make that work.

Please help.

Baltazar
Comments: The "$safeprojectname$ is added by program. Can you send a example program? It is easier if you send a simple example. VS Studio Express 2012 TIA

Edited Issue: LocalizeDictionary.DesignCulture & Blend + VS2012 [9269]

MrCircuit — Tue, 09 Apr 2013 07:19:28 GMT

Blend and VS 2012 do not react properly on the value of LocalizeDictionary.DesignCulture.

This is caused by the designer not uploading the satellite assemblies to the ShadowCache path, e.g.:

[User]\AppData\Local\Microsoft\VisualStudio\11.0\Designer\ShadowCache

Edited Issue: LocalizeDictionary.DesignCulture & Blend + VS2012 [9269]

MrCircuit — Tue, 09 Apr 2013 07:18:59 GMT

Edited Issue: LocalizeDictionary.DesignCulture & Blend + VS2012 [9269]

MrCircuit — Mon, 08 Apr 2013 07:00:49 GMT

Blend and VS 2012 do not react properly on the value of LocalizeDictionary.DesignCulture.

This is caused by the designer not uploading the satellite assemblies to the ShadowCache path, e.g.:

C:\Users\uwe.mayer\AppData\Local\Microsoft\VisualStudio\11.0\Designer\ShadowCache

Commented Issue: Windows Store App support [9279]

MrCircuit — Sun, 07 Apr 2013 13:03:20 GMT

Hi,

are Windows Store Apps supported? If not: is a support planned, or do you know a good alternative for runtime localization? This project is looking realy nice *.*

I just tried to install the Package via NuGet and got an Error:

Attempting to resolve dependency 'XAMLMarkupExtensions (≥ 1.1.5)'.
Successfully installed 'XAMLMarkupExtensions 1.1.5'.
Successfully installed 'WpfLocalizeExtension 2.1.2'.
The process cannot access the file 'c:\Users\xxx\documents\visual studio 2012\Projects\TestApp\packages\XAMLMarkupExtensions.1.1.5\lib\net35\XAMLMarkupExtensions.dll' because it is being used by another process.
The process cannot access the file 'c:\Users\xxx\documents\visual studio 2012\Projects\TestApp\packages\XAMLMarkupExtensions.1.1.5\lib\net40\XAMLMarkupExtensions.dll' because it is being used by another process.
The process cannot access the file 'c:\Users\xxx\documents\visual studio 2012\Projects\TestApp\packages\XAMLMarkupExtensions.1.1.5\lib\sl50\XAMLMarkupExtensions.dll' because it is being used by another process.
The directory is not empty.

Successfully uninstalled 'XAMLMarkupExtensions 1.1.5'.
Install failed. Rolling back...
Could not install package 'XAMLMarkupExtensions 1.1.5'. You are trying to install this package into a project that targets '.NETCore,Version=v4.5', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

regards

otis
Comments: Hi otis, Sorry for the late answer. I tried digging into this but could not get an RT version to run due to the restricted .NET core content. I would suggest using the built-in localization feature of RT (although not providing runtime language switching as far as I know). Best regards, Uwe

Closed Issue: Edit DesignCulture on the VS12 Designer [9286]

MrCircuit — Sun, 07 Apr 2013 12:59:57 GMT

Commented Issue: Edit DesignCulture on the VS12 Designer [9286]

kroimon — Sat, 06 Apr 2013 22:29:29 GMT

Hi, your work is great !!!
I've done a small tuto project on visual studio 12 and when I edit, the DesignCulture in the xaml, the designer crash with different issues.

The project was built on VS10 and I work also with Blend 4 on Win7.
If I try my tuto project with VS10, that works perfectly.
Comments: Please see my post in the discussion forum: https://wpflocalizeextension.codeplex.com/discussions/415165 The XAML Designer crashes when setting `Thread.CurrentThread.CurrentUICulture` to anything but the installation culture (for me, anything but "de").

Commented Issue: Edit DesignCulture on the VS12 Designer [9286]

MrCircuit — Fri, 05 Apr 2013 13:51:28 GMT

Hi, your work is great !!!
I've done a small tuto project on visual studio 12 and when I edit, the DesignCulture in the xaml, the designer crash with different issues.

The project was built on VS10 and I work also with Blend 4 on Win7.
If I try my tuto project with VS10, that works perfectly.
Comments: The spanish language is missing as the designer only uses one sattelite assembly. (same as for Blend before) I've set up a question on the WPF forums of Microsoft.

Commented Issue: LocalizeDictionary.DesignCulture & Blend [9269]

MrCircuit — Fri, 05 Apr 2013 13:50:28 GMT

In some cases, Blend does not react properly on the value of LocalizeDictionary.DesignCulture.
Comments: I've set up a question on the WPF forums of Microsoft.

Closed Issue: VB .NET Assembly with dots [9287]

MrCircuit — Fri, 05 Apr 2013 11:57:44 GMT

Closed Issue: Default Dictionary name to be Resources [9275]

MrCircuit — Fri, 05 Apr 2013 10:47:55 GMT

It's quite annoying having to create three lines in every wpf control/window you create

lex:LocalizeDictionary.DesignCulture="en"
lex:ResxLocalizationProvider.DefaultAssembly="Security.Module"
lex:ResxLocalizationProvider.DefaultDictionary="Resources"

Most of the times the Default Dictionary will be the default Resources. So why not make "Resources" the default value of the attached property? This reduces even more the amount of code required to use the WPF Localization Extension.

Also, The value of the Default Assembly attached property could be the assembly of the control using the WPF Localization Extension.

Thanks!