Nopcommerce architecture Analysis of eight------multi-lingual

The language supported by the system is a class: language expression;

The corresponding classes of multi-language resources are: Localizedproperty;

Yourselves select a language to store in the class: Genericattribute;

Multiple languages can be exported as XML files, and of course, export is also supported.

Iworkcontext and its entity classes are webworkcontext the current run context, and the user's login information and some contextual settings are saved in this class.

Details include: Current user information: Currentcustomer; current user cookie; currency; language; type of tax; supplier, etc.;

There are several ways to show multilingual resources:

First, in the custom class Webviewpage<tmodel> put the method: T (), through this method, the Web page in the presentation of the corresponding language to obtain the text.

In fact, T is just a proxy, the agent is defined as:

[CSharp]View PlainCopy

1. Namespace Nop.Web.Framework.Localization
2. {
3. public Delegate localizedstring Localizer (string text, params object[] args);
4. }

This proxy returns a value of type localizedstring, which inherits the interface ihtmlstring to ensure that localized text resources are displayed correctly.

The ihtmlstring is defined as:

[CSharp]View PlainCopy

2. Summary:
4. //Represents an HTML-encoded string that should not be encoded again.
6. public interface ihtmlstring
8. {
10. //Abstract:
12. //Returns an HTML-encoded string.
14. //  
16. //Return Result:
18. //HTML-encoded string.
20. string tohtmlstring ();
22. }

Second, through the expansion of HtmlHelper

Class Htmlextensions extends the HtmlHelper class,

It is mainly for the encapsulation of some controls and supports multiple languages.

Method Localizededitor<t, Tlocalizedmodellocal> is the encapsulation of the Telerik TabStrip control (that is, the Multi-tab Control---tab control). When the system supports multiple languages, it displays a tab for each language, but only when needed. The interface Ilocalizedmodel and interface ilocalizedmodellocal are used in this area. The interface Ilocalizedmodel is used to indicate that a model class supports this multi-language display, which includes multiple language data lists locales, the class that implements the interface ilocalizedmodellocal is the data of a particular language. The Localizededitor method is to implement support for multiple language page signatures based on the interface's mates. The admin project uses this method, and the Web project is not used.

[CSharp]View PlainCopy

2. Public static Helperresult localizededitor<t, tlocalizedmodellocal> (thishtmlhelper<t> helper, string name,
4. func<int, helperresult> localizedtemplate,
6. Func<t, helperresult> standardtemplate)
8. where t:ilocalizedmodel<tlocalizedmodellocal>
10. where tlocalizedmodellocal:ilocalizedmodellocal
12. {
14. return new Helperresult (writer =
16. {
18. if (helper. ViewData.Model.Locales.Count > 1)
20. {
22. var TabStrip = helper. Telerik (). TabStrip (). Name (name). Items (x =
24. {
26. X.add (). Text ("standard"). Content (Standardtemplate (helper). Viewdata.model). Tohtmlstring ()).  Selected (true);
28. For (int i = 0; i < helper. ViewData.Model.Locales.Count; i++)
30. {
32. var locale = helper. Viewdata.model.locales[i];
34. var language = enginecontext.current.resolve<ilanguageservice> (). Getlanguagebyid (locale. LanguageID);
36. X.add (). Text (language. Name)
38. . Content (localizedtemplate
40. (i).
42. Tohtmlstring
44. ())
46. . IMAGEURL ("~/content/images/flags/" + language.  Flagimagefilename);
48. }
50. }). Tohtmlstring ();
52. Writer. Write (TabStrip);
54. }
56. Else
58. {
60. Standardtemplate (helper. Viewdata.model). WriteTo (writer);
62. }
64. });
66. }

Extension method Noplabelfor<tmodel, tvalue> is another way to implement multiple languages.

This method mainly implements the description of the property name based on the subclass nopresourcedisplayname of the attribute Displaynameattribute. This attribute is a modification to the Model property to specify the name of the property.

For example, the properties of a class Addnewscommentmodel are specified with the Nopresourcedisplayname attribute:

[CSharp]View PlainCopy

2. Namespace Nop.Web.Models.News
4. {
6. Public partial class Addnewscommentmodel:basenopmodel
8. {
10. [Nopresourcedisplayname ("News.Comments.CommentTitle")]
12. [Allowhtml]
14. public string Commenttitle { get;  set;}
18. [Nopresourcedisplayname ("News.Comments.CommentText")]
20. [Allowhtml]
22. public string Commenttext { get;  set;}
26. public bool Displaycaptcha { get;  set;}
28. }
30. }

The implementation of the HtmlHelper extension method noplabelfor is as follows:

[CSharp]View PlainCopy

2. Public static mvchtmlstring Noplabelfor<tmodel, tvalue> (thishtmlhelper<tmodel> helper, Expression<func<tmodel, tvalue>> expression, bool Displayhint = true)
4. {
6. var result = new StringBuilder ();
8. var metadata = modelmetadata.fromlambdaexpression (expression, helper. ViewData);
10. var hintresource = string.  Empty;
12. object value = null;
14. if (metadata. Additionalvalues.trygetvalue ("Nopresourcedisplayname", out value))
16. {
18. var resourcedisplayname = value as nopresourcedisplayname;
20. if (resourcedisplayname! = null && displayhint)
22. {
24. var langId = enginecontext.current.resolve<iworkcontext> (). Workinglanguage.id;
26. Hintresource =
28. Enginecontext.current.resolve<ilocalizationservice> ()
30. . GetResource (Resourcedisplayname.resourcekey + ".  Hint ", langId);
34. Result. Append (helper. Hint (Hintresource). Tohtmlstring ());
36. }
38. }
40. Result. Append (helper.  Labelfor (expression, new {title = Hintresource});
42. return mvchtmlstring.create (result.  ToString ());
44. }

Nopcommerce architecture Analysis of eight------multi-lingual