locked
XsltListViewWebPart & MUI RRS feed

  • Question

  • Is there anyway how can I localize XsltListViewWebPart ? So that wp support multi language user interface ?

     

    I cannot even create custom wp and inherit it from XsltListViewWebPart, becase it's sealed :(

     


    Martin ---------------------------------------------------- Martin Pawlas, MCTS, MCP
    Monday, November 28, 2011 2:02 PM

Answers

  • Please check links-

    http://msdn.microsoft.com/en-us/library/ff806155.aspx

    http://msdn.microsoft.com/en-us/library/ff806164.aspx

    You can make resource strings available to XSLT transforms in one of two ways:

    • As style sheet parameters (<xsl:param>) that are retrieved through <ParameterBinding> tags in the Web Part (see ParameterBinding).

    • As XPath expressions that are used in <xsl:value-of> tags.

    The ParameterBinding element includes a Location attribute that specifies resource types. The syntax for this element is similar to the ASP.NET resource binding expression syntax:

    <ParameterBinding Name=” parameterName ” Location=”Resource( resourceFile , resourceName )” />

     

    Hope this helps you:)

    Regards,

    Sushil

    • Marked as answer by Shimin Huang Wednesday, December 7, 2011 9:45 AM
    Tuesday, November 29, 2011 10:51 AM
  •  

    Try with below sample code to read web part title from resource files.

    <WebPartPages:XsltListViewWebPart runat="server" IsIncluded="True" GhostedXslLink="maint" ListUrl="Lists/customlist
                       NoDefaultStyle="TRUE" ViewFlag="8" Title="<%$ Resources:reportserver,ReportExecution %>" PageType="PAGE_NORMALVIEW"
                                Default="FALSE" DisplayName="<%$ Resources:reportserver,ReportExecution %>" __markuptype="vsattributemarkup"
                                PartOrder="2" ID="wpltListViewDocumentUpload" ViewContentTypeId="0x" Visible="true">

    ....

    Hope Mutillinual sites is configured -http://technet.microsoft.com/en-us/library/ff805087.aspx

     

    Regards,

    Sushil

     

    • Marked as answer by Shimin Huang Wednesday, December 7, 2011 9:45 AM
    Tuesday, December 6, 2011 11:38 AM

All replies

  • Please check links-

    http://msdn.microsoft.com/en-us/library/ff806155.aspx

    http://msdn.microsoft.com/en-us/library/ff806164.aspx

    You can make resource strings available to XSLT transforms in one of two ways:

    • As style sheet parameters (<xsl:param>) that are retrieved through <ParameterBinding> tags in the Web Part (see ParameterBinding).

    • As XPath expressions that are used in <xsl:value-of> tags.

    The ParameterBinding element includes a Location attribute that specifies resource types. The syntax for this element is similar to the ASP.NET resource binding expression syntax:

    <ParameterBinding Name=” parameterName ” Location=”Resource( resourceFile , resourceName )” />

     

    Hope this helps you:)

    Regards,

    Sushil

    • Marked as answer by Shimin Huang Wednesday, December 7, 2011 9:45 AM
    Tuesday, November 29, 2011 10:51 AM
  • all right, but what about web part title
    Martin ---------------------------------------------------- Martin Pawlas, MCTS, MCP
    Tuesday, November 29, 2011 11:09 AM
  •  

    Try with below sample code to read web part title from resource files.

    <WebPartPages:XsltListViewWebPart runat="server" IsIncluded="True" GhostedXslLink="maint" ListUrl="Lists/customlist
                       NoDefaultStyle="TRUE" ViewFlag="8" Title="<%$ Resources:reportserver,ReportExecution %>" PageType="PAGE_NORMALVIEW"
                                Default="FALSE" DisplayName="<%$ Resources:reportserver,ReportExecution %>" __markuptype="vsattributemarkup"
                                PartOrder="2" ID="wpltListViewDocumentUpload" ViewContentTypeId="0x" Visible="true">

    ....

    Hope Mutillinual sites is configured -http://technet.microsoft.com/en-us/library/ff805087.aspx

     

    Regards,

    Sushil

     

    • Marked as answer by Shimin Huang Wednesday, December 7, 2011 9:45 AM
    Tuesday, December 6, 2011 11:38 AM