Hi,
is there a way to use TxTranslation inside DataTrigger Setters?

First of all thank a lot for the great, convenient and awesome library! It is perfect!
Unfortunately it can not be applied to mobile development Xamarin Forms for example. And it is very sad
Have you plan port it in cross-platform PLC library ?

I'm not sure if this behavior is intentional, but it is not how I understood the documentation.

Say you have a txd file with English (as primary) and French cultures, and a key that intentionally only has a translation for english:

<?xml version="1.0" encoding="utf-8"?>
<!-- TxTranslation dictionary file. Use TxEditor to edit this file. http://unclassified.software/txtranslation -->
<translation xml:space="preserve">
	<culture name="en" primary="true">
		<text key="minimum" comment="The english translation works also for french">Min</text>
	</culture>
	<culture name="fr" />
</translation>

Then Tx.SetCulture("fr"); Tx.T("minimum"); would result in "Min" as intended.

The TxEditor shows a "Missing translation" as a problem for that key, so you click on that (so it gets a green checkmark) to accept the inconsistency and mark it as intentional. This results in:

<?xml version="1.0" encoding="utf-8"?>
<!-- TxTranslation dictionary file. Use TxEditor to edit this file. http://unclassified.software/txtranslation -->
<translation xml:space="preserve">
	<culture name="en" primary="true">
		<text key="minimum" comment="The english translation works also for french">Min</text>
	</culture>
	<culture name="fr">
		<text key="minimum" acceptmissing="true" />
	</culture>
</translation>

With that file, the behavior is now different, and Tx.SetCulture("fr"); Tx.T("minimum"); results in an empty string.
I expected this to only affect the behavior in the TxEditor, not the actual translation.

What am I missing, the documentation does not contain an actual guide on how to set up so I had to feel around in the dark. I have the library and am correctly (i think) trying to translate a peice of text using <TextBlock Text="{Tx:T Announcements}"/> I also created and saved a dictionary to my bin/debug folder called localization.txd, but how do I actually tie this dictionary to my project?

Do you plan on supporting .Net Standard / .Net Core? I am currently using your software (love it BTW), but need to convert my software to .Net Standard. Will you be updating the nuget package to contain a .Net Standard build?

Thanks.

Hello, Thank you very much for your library. It's very helpful. But I'm new one with that and do everything that in documentation and I can't make it work properly. Could you answer me on stackoverflow?

http://stackoverflow.com/questions/35480572/txtranslation-wpf-application

Thank you again.
Kind regards.

Features that i require:

1. Multiple dictionary files editing.
2. UI improvement(arguments description for specific key etc)
3. Drag'n'drop support tree
4. Partial key templates for common element description (commands, forms etc)

So I must to decide what to do:

1. Rework UI core (I am afraid that it will broke backward compatibility with your current master state or pull requests will be huge)
2. Add this features externally with out core rewriting (add additional pane for multiple files).

I will choose 2 if you interested in your master Editor improvement. If you do not care about requested features I will choose 1.

TxLib stores its translations in a static dictionary. Imagine you have your application A.exe that uses TxLib.dll version A. Now A.exe has plugin support and can be enriched by the plugin B.dll. B.dll uses another version of TxLib.dll version B.
The second the plugin reaches a method that access the static Tx.T fuction (or any other static function) TxLib.dll version B will get loaded and the static class constructor will initialize the static dictionary. This leads to a loss of translations for the loaded assembly TxLib.dll version A.

This issue is so apparent it even sometimes breaks unit tests that run in parallel, all using TxLib: In the instance another test accesses the static Tx.T function (or any other) the test itself cannot access the translation any longer.

I propose to add a non-static constructor and non static functions. Then the translation objects can live next to each other. For backward compatibility one could offer a static Default TxLib object, that uses the same non-static ctor and all static functions use that (static) instance.

Hi! Great project :)

I have the problem with updating *.txd file via TxEditor.
When i update it via TxEditor, MainWindow.xaml form of project WpfDemo doesn't update.
If i do it via any text editor (e.g. notepad++) it works.
Could you help me with this problem?

Shouldent design time show the default text, or at least the key?

NuGet package: Fluent.Ribbon

Reference: dotnetpro 2016-09/76

Hi!
I'm trying to build my application to deploy via clickonce and get following error:

Assembly generation failed -- Referenced assembly 'Unclassified.TxLib' does not have a strong name

Could you sign your assembly and update your nuget package?

Hi,

we are loading dictionaries from both an embedded resource and from XML files.
The embedded resource acts as a fallback when the user does not provide a complete txd file.

When we have Tx.UseFileSystemWatcher = true, and modify a txd file, the keys from the embedded resource get thrown away.

This is kind of counter-intuitive, and I don't think there is a workaround for it.
IMHO, Tx.CheckReloadFiles() should not overwrite the entire global dictionary.