even in 2.0 its okay but i want immediately pls some one help me -- i dnt know why iwas unable to add fig input file en-us.xlf input file (pls drop your email ids i can forward you the question)
Requirements:
The tool should be able to perform the following:
- Open an existing XLIFF file
- Save the modified XLIFF file
- Display the Id (read only)
- Display the un-translated text (read only)
- Display and edit the translated text (read/write)
- Changing the text should automatically change the state to translated
- Display and edit the translation state as a Boolean (is translated – read/write). XLIFF supports multiple states; this tool only cares about translated and needs-translation.
- Allow filtering the displayed data by (filtering will take place when the Apply Filters buttons is clicked):
- Id
- Un-translated text sub-string
- Translated text sub-string
- Filtered state
Suggested UI:
Input:
Use this sample XLIFF file to test the tool.
{{{{Ç En-us.xlf C:\FRAMEW~1\DFuse\PLATFO~1\Src\UI\LANGUA~1\FRAMEW~1\en-US.xlf > C:\FRAMEW~1\DFuse\PLATFO~1\Src\UI\LANGUA~1\FRAMEW~1\en-US.xlf 1
Output:
The output should be a VS 2008 project and source that meets the above requirements. The code should be written in C# and make use of .Net 3.5 technologies including WPF.
Suggestions:
Determine a load strategy – XmlDocument, LinqToXML, etc
Try to use XAML for displaying the data.
Use Data where appropriate. Bind Dependency Properties for the UI controls in XAML to the data Binding.
Use a ValueConverter to convert the XLIFF state to a boolean
mohanPosted Jul 28, 2008, 3:50 PM
ANy luck on this.
Pl reply me [email protected]
Regs
Mohan
mohanPosted Jul 28, 2008, 1:17 PM
Ravi do let me know if you find any solution.
Thanks in advance
-- Mohan