[Mono-bugs] [Bug 522561] New: mono2.4 add-on runtime does not work for non-english languages
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Thu Jul 16 02:09:29 EDT 2009
http://bugzilla.novell.com/show_bug.cgi?id=522561
Summary: mono2.4 add-on runtime does not work for non-english
languages
Classification: Mono
Product: Mono: Runtime
Version: 2.4.x AddOn CD
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: misc
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: kuanil at novell.com
QAContact: mono-bugs at lists.ximian.com
Found By: Third Party Developer/Partner
Created an attachment (id=305445)
--> (http://bugzilla.novell.com/attachment.cgi?id=305445)
The test case files bindled in tar
iFolder bundles the generated resource files alongwith its own DLL and uses
that to display non-english strings on UI.
The attached test case generates the resource files and tries to get the
language specific strings using "GetString()" API. Problem is that, the
resource files are generated successfully using mono 2.4 add-on as required,
but during runtime, GetString() API fails to get the lnaguage specific string
and it displays the default english language .
If i use older mono version, then it generates the resource files and also
GetString() passes.
One other observation : The test.exe generated by mono2.4 add-on, when i try to
run this exe using older 'mono' command then it works. So in summary, mono 2.4
addon runtime fails to get the strings from resource files.
Steps used to reproduce:
1. Extract the tar 'Resource_Sample.tar'.
2. run 'source' command to get the mono2.4 add-on environment.
3. ./build.sh
4. mono test.exe
Expected result: It should display the language specific string.
Actual Result : It displays default english language.
Because of this bug, iFolder does not work for non-english language and we have
a critical bug for this.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list