כניסה
 
עמוד הביתספריהלמדהורדותאיתר וטיפל בבעיותקהילהפורומים
משאבים למומחי מחשוב >
> 
> 
Unable to add language to UAG portal

Proposed Unable to add language to UAG portal

  • יום שישי 29 אפריל 2011 11:21
     
     
    היכנס כדי להצביע
    0

    Hi!

    I'm trying to add the swedish language to UAG and it's partly working. The goal is to have UAG automaticaly select the language configured in the client browser without displaying "choose language" to the user. This is what i have done:

    Copied the default en-US language files for internalsite and portalhompage to their respective customupdate folders. Renamed the files to sv-SE.xml and translated them to swedish. I've also copied languages.xml from internalsite to the customupdate folder and added swedish to the list of languages.

    Now everything works fine at the login page (internalsite) including all messages, pop-ups and so on but when loged in and the portalhomepage is displayed it defaults to the en-US laguage file. Even if i enable manual language selection for the user the result is the same. While troubleshooting i copied the default en-US file for portalhomepage  to the customupdate folder and edited it to see if it at all tries to read from customupdate, and it does. Since this is a multi trunk setup i've also tried to name the language file trunk1sv-SE.xml without luck and i didn't expect it to either. If i understand custization correctly that naming syntax i for portal customization but doesn't apply to languages, right? How do i get UAG to display the new language in the portalhomepage for all trunks?

    Thanks in advance!

    btw. The UAG Version is SP1 Rollup1.

    /Joakim

     

כל התגובות

  • יום רביעי 04 מאי 2011 08:18
     
     
    היכנס כדי להצביע
    1

    Hi Joakim,

    Have you managed to solve this or do you still have the problem? Let me know and I can try to offer a few pointers.

    Regards,

    -Ran
     
  • יום שלישי 31 מאי 2011 18:36
     
     
    היכנס כדי להצביע
    0

    Hi Ran,

    Thank you for offering your help!

    Unfortenately i didn't get an email alert of your response so i assumed that no one hade any answers. Sorry about that. i would gladely accept some pointers even though i've already opened a support case with Microsoft.

    I unmarked your answer as a solution only to reopen the thread and post back our findings. I'm sure i am not the only administrator in the world that at some time would like to add a language to UAG :)

    Hopefylly i can post back something useful soon.

    Regards,

    /Joakim

     
  • יום רביעי 01 יוני 2011 04:48
     
     
    היכנס כדי להצביע
    0

    Hi Joakim,

    Could you please share here your SR number, so that I could take care of it as well as answering you here?

    Thanks,

     

    -Ran
     
  • יום רביעי 01 יוני 2011 07:40
     
     
    היכנס כדי להצביע
    0

    Hi,

    The case is assigned to Els Krüger and he has set up a lab environment and been sent the language files we've used to replicate the issue.

    The SR number is 111051939524286.

    /Joakim

     
  • יום רביעי 01 יוני 2011 08:13
     
     הצעה לתשובה
    היכנס כדי להצביע
    0

    Thanks,

    I'm taking a look and I will let you and the community know, here in the Forum.

    Regards,

    -Ran
     
  • יום שני 06 יוני 2011 08:08
     
     
    היכנס כדי להצביע
    0

    Hi Joakim,

    Have you had the time to test the solution that was provided to you by Microsoft Support almost a week ago?

    As mentioned in the solution sent to you, when adding a new language XML file to the \von\Portal\Data\Languages\CustomUpdate folder (for example se-SV.xml for Swedish), that file is not taken into account by UAG unless a file with the same name also exists in the parent folder \von\Portal\Data\Languages. The file in the root folder does not need to actually contain strings definitions, it can be an almost empty XML file, but it has to exist there. For example, the file can be like this:

    <Strings>

    </Strings>

     

    HTH,

     

    -Ran
     
  • יום שלישי 07 יוני 2011 12:23
     
     
    היכנס כדי להצביע
    0

    Hi Ran,

     

    After five days of Swedish national holidays i'm now back online :)

    Yes i've tried it and it didn't work though i did some research on my own based on his suggestion and found a workaround. Instead of creating a dummy file as suggested i copied my actual language file to the language root fioder of portalhomepage. This is great news  since i and the customer can now move forward in the project but we can not see this as anything else but a workaround.

    I hope it's possible to coorrect the UAG with a patch so that no modifications outside of customupdate folders are needed and in that way securing the functionality of future updates and backup/restore scenarios.

    Regards

    Joakim

     
  • שבת 24 ספטמבר 2011 10:10
     
     
    היכנס כדי להצביע
    0

    Hi Joakim

     

    Use you still using your workaround for portal language or have find out something else?

     

    I have exactly the problem. My login page translates fine depending browser language, needed files in my case are english and finnish. Portal page doesn't translate to finnish. I've found out couple of funny things: if i change my browser language to Germany portal translater ok and all other built-in languages work fine. Only finnish is the problem and i think swedish also.

     

    And last i tested my portal configuration with Windows xp sp3 and portal configuration worked fine. Both, login page and portal page, got translated depending on browser language. Previous test was done with Windows 7 sp1.

     

    Does your portal work the same way? And i'm open to ideas.

    Thanks

    br -teemu
     
  • יום שלישי 27 ספטמבר 2011 20:45
     
     
    היכנס כדי להצביע
    0

    Hi Teemu,

    Yes, I'm still using the suggested workaround but with the twist described in my previous post.

    Are you using automatic language setting based on the language configured in client InternetExplorer or do you let the users choose language them selves? If you are using automatic, that is not displaying the language choice setting on login page, then try the following.

    (I assume that you have your finnish language file in the language customupdate folder both internal site and portalhomepage and a copy of your finnish language file in the default location of language files fort the portalhomepage already. Don't forget to add finnish to the language.xml. )

    1. Clear browser temporary files and cookies on client.

    2. add the language choice setting to the login page and activate UAG configuration.

    3. Connect to the UAG with your finnish client. Finnish will most probably be your default language setting. Before you log in, change the language to which ever you like. Eg. german. Then back to finnish again. Now log in and both log in page and portal should be in finnish.

    Let me know how it works out :)

     

    FYI, I'm running a business case together with a customer and Microsoft in Sweden about this issue and how it affects customers choice of product. It might seem lika a minor issue to all you who speaks english, or any other of the included languages, natively but for all of us operating in regions who don't...       

    We'll see how it turns out.

     

    Regards

    Joakim

     
  • יום רביעי 28 ספטמבר 2011 20:27
     
     
    היכנס כדי להצביע
    0

    Hello Joakim

    I tried what you suggested and it worked! Portalhomepage translated to finnish after i selected another language from login page's drop down menu and then changed back to finnish.

    Only problem for me is that the plan is to detect language automatically without dropdown menu :). I'm using radius for authentication and i've translated radius messages by detecting language automatically and based on that information selecting correct radius repository (i've got radius repositories configured in english and finnish).

    This workaround is really great to know but i hope it would be possible to use automatic detection. Also my customer would be happier :). Anyway i think this could be usable solution if i force default language and then user would have to select own language.

    I have also opened a MS support case about this. We'll see how it goes..

     

    Thanks

    br -teemu
     
  • יום חמישי 29 ספטמבר 2011 00:00
     
     
    היכנס כדי להצביע
    0

    Teemu,

    I forgot to tell you. You can now remove the manual language setting from the UAG log in page again, and the translations should continue to work. Now with automatic language selection.

    /Joakim

     



    • נערך על-ידי Joakim Hogstrom יום חמישי 29 ספטמבר 2011 15:58
    •  
     
  • יום שלישי 31 ינואר 2012 15:55
     
     
    היכנס כדי להצביע
    0

    I am trying to add the welsh language onto our portal and am having real problems doing so. The language selection works on the log screen (internal site) and I can select welsh and the text on the page will change to welsh as expected. However text on the portal page for applications will not change and will default to English.

    I have done the following things following the guidance on this thread but with no luck:

    • Adding the setting   <Language id="cy-UK">Cymraeg</Language> into the
      von\InternalSite\Languages\Languages.xml file (I presume this part works as this option then appears in the language selection box on the log on page)
    • Creating a custom cy-UK.xml file and placing this in the \von\InternalSite\Languages\CustomUpdate folder and changing string settings in there (this also works as when I select the welsh language in the drop down the relevant text is changed on the page.)
    • Created a custom cy-UK.xml file in \von\PortalHomePage\Data\Languages and added an element like this
      <String id="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4">Welsh name</String>
      <String id="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4"> Welsh Application short description</String>
      <String id="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4">Welsh Application long description</String>
    • Also created a custom en-US.xml file and placed this in the same folder and added the xml element:<String id="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4">English name</String>
        <String id="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4">English Application short description</String>
        <String id="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4">English Application long description</String> 
    • On the advice from this thread created a cy-UK.xml file in \von\PortalHomePage\Data\Languages and just left it with a <String> entry.

    But...no luck however if I add a custom file i.e de-DE.xml in the custom update folder and add the custom application text it works! As mentioned on here it seems to work for default languages but not those created manually. Unfortunately  if I can't get this issue resolved it will no doubt end in the failure of the project which is not good!

     
  • יום שלישי 31 ינואר 2012 23:42
     
     
    היכנס כדי להצביע
    0

    Hi,

    The language entry with just a <String> entry never worked for me either...

    Try this: Remove the cy-UK.xml you created from \von\PortalHomePage\Data\Languages. Make a copy of en-US.xml in \von\PortalHomePage\Data\Languages and rename it cy-UK.xml.

    Btw, are you presenting the option to choose language at login? If you are not, the login page will automatically display the preferred browser language but the portal itself will default to en-US.

    Hope this helps! :) ...if not, just let me know and i'll help you sort it out.

    After all, we don't want you project to fail :)

    Regards

    Joakim

     

     
  • יום רביעי 01 פברואר 2012 09:49
     
     
    היכנס כדי להצביע
    0

    Hi Joakim,

                   Many thanks for your reply, I really appreciate it. I tried what you suggested but unfortunately it didn't work, I still get the English version rather than the Welsh! I am presenting the option to chose language at log on, and the frustrating thing is if I create a custom de-DE.xml file and place it in the custom update folder and add the application entries it works when I select German from the drop down list on the log on page! When I select Welsh it changes the language on the log on page but not in the portal. I wonder if there are any logs I can look at to see what is happening during the activation of the web site so I can where I am going wrong!! I am running UAG version 4.0.1773.10110.

    Many thanks,

    Pete

     
  • יום שלישי 21 פברואר 2012 10:03
     
     
    היכנס כדי להצביע
    0

    Hi Pete,

    I'm sorry for the late reply :( Private family matters came in the way...

    Did you get it to work?

    My suggestion would otherwise be to copy the original en-US files, rename them to cy-UK and the replace the contents.

    Regards

    Joakim

     
  • יום חמישי 01 מרץ 2012 16:00
     
     
    היכנס כדי להצביע
    0

    Hi Joakim,

                   Unfortuately no success, I've tried what you suggested but no luck! I'll keep trying, very frustrating though!

    Pete

     
  • יום שישי 02 מרץ 2012 00:09
     
      קוד כלול
    היכנס כדי להצביע
    0

    Hi Pete,

    Here's what i would do:

    • Remove all language customization files for cy-UK that you have created (rename them or something). If everything works as expected at logon page(/InternalSite/Languages/CustomUpdate) only remove your files for the portal (/PortalHomePage/Data/Languages and /CustomUpdate). I'll assume you have removed all language customization files in this guide.
    • Copy Languages.xml from /InternalSite/Languages to /InternalSite/Languages/CustomUpdate. Open Languages.xml and add "<Language id="cy-UK">Cymraeg</Language>", save and close.
    • Copy en-US.xml from /InternalSite/Languages to /InternalSite/Languages/CustomUpdate. Rename the file to cy-UK.xml, open it and change something simple that is easy to spot when the login page is accessed. Example: change "<String id="2" _locID="2">Application and Network Access Portal</String>" to "<String id="2" _locID="2">Cymraeg Application and Network Access Portal</String>", save and close.
    • Copy en-US.xml from /PortalHomePage/Data/Languages to /PortalHomePage/Data/Languages/CustomUpdate and rename the file to cy-UK.xml. Again, open it and change something simple that is easy to spot when the portal is accessed. Example: change "<String id="12" _locID="12">Application and Network Access Portal</String>" to "<String id="12" _locID="12">Cymraeg Application and Network Access Portal</String>". Now go to the bottom of the file and add your custom application strings like this:
    <String id="313" _locID="313">
    <!-- _locID_CDATA="HTM" --><![CDATA[<OL>
                                <LI>To view activity of legacy applications, click <B>Activity</B> on the toolbar.</LI>
                                </OL>]]></String>
    <String id="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4">Welsh name</String>
    <String id="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4"> Welsh Application short description</String>
   <String id="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4">Welsh Application long description</String>
</Strings>

                     save and close.

    • Copy the cy-UK.xml you just created in  /PortalHomePage/Data/Languages/CustomUpdate to  /PortalHomePage/Data/Languages.
    • Activate the configuration.

    Important to keep in mind when testing is that the login page (InternalSite) detects the language setting of the connecting browser and tries to match the setting. If the browser has cy-UK as its preffered languange and cy-UK exists in Languages.xml it'll be displayed, otherwise it defaults to en-US. BUT, in order for the portal(PortalHomePage) to display cy-UK.xml there must be a cookie set from the login page. This cookie is NOT automatically set when the login page is loaded, even if the correct language is matched. Without this cookie the portal will default to en-US regardless of the language displayed at login page. To force the UAG to set the cookie, the user must change language(en-US) and then change back to the desired language(cy-UK) at the login page before login.

    I have a fix for that as well  but let's just take one step at the time. Remember to check your xml-files for syntax error before testing(open in IE or something). That usually saves a lot of time :)

    Good Luck Pete! :)

    Regards
    Joakim


    • נערך על-ידי Joakim Hogstrom יום שישי 02 מרץ 2012 00:12
    •  
     
  • יום שלישי 13 מרץ 2012 21:16
     
     
    היכנס כדי להצביע
    0

    What if you ony add the new file directly to the language folder? and leave the language.xml untouched.

    It worked for me.

    Place a translated nl-NL.xml in \InternalSite\Languages\

    Added a reference to the language.xml resulted in a 500. Removing the entry from language.xml and my page was in the correct language.

    Have not tried this for PortalHomePage though.

    Hope it helps,

    Bart

     
  • יום שלישי 29 מאי 2012 07:57
     
     
    היכנס כדי להצביע
    0

    What if you ony add the new file directly to the language folder? and leave the language.xml untouched.

    It worked for me.

    Place a translated nl-NL.xml in \InternalSite\Languages\

    Added a reference to the language.xml resulted in a 500. Removing the entry from language.xml and my page was in the correct language.

    Have not tried this for PortalHomePage though.

    Hope it helps,

    Bart

    Hi Bart,

    I am looking to translate our Portal to Dutch aswell but I was wondering is you are willing to sent me your translation? It would save me a lot of work.

    Many thanks,

    Roy

     
  • יום שני 14 ינואר 2013 15:04
     
     
    היכנס כדי להצביע
    0

    What if you ony add the new file directly to the language folder? and leave the language.xml untouched.

    It worked for me.

    Place a translated nl-NL.xml in \InternalSite\Languages\

    Added a reference to the language.xml resulted in a 500. Removing the entry from language.xml and my page was in the correct language.

    Have not tried this for PortalHomePage though.

    Hope it helps,

    Bart

    Hi Bart,

    I am looking to translate our Portal to Dutch aswell but I was wondering is you are willing to sent me your translation? It would save me a lot of work.

    Many thanks,

    Roy


    Hi Bart,

    I would also like to add the Dutch language to the portal, can you please send me your translation?

    Thanks!

    Laris


    • נערך על-ידי Systems.ZA יום שני 14 ינואר 2013 15:05
    •  
     
  • יום שלישי 22 ינואר 2013 14:54
     
      קוד כלול
    היכנס כדי להצביע
    0

    Hi Pete,

    Here's what i would do:

    • Remove all language customization files for cy-UK that you have created (rename them or something). If everything works as expected at logon page(/InternalSite/Languages/CustomUpdate) only remove your files for the portal (/PortalHomePage/Data/Languages and /CustomUpdate). I'll assume you have removed all language customization files in this guide.
    • Copy Languages.xml from /InternalSite/Languages to /InternalSite/Languages/CustomUpdate. Open Languages.xml and add "<Language id="cy-UK">Cymraeg</Language>", save and close.
    • Copy en-US.xml from /InternalSite/Languages to /InternalSite/Languages/CustomUpdate. Rename the file to cy-UK.xml, open it and change something simple that is easy to spot when the login page is accessed. Example: change "<String id="2" _locID="2">Application and Network Access Portal</String>" to "<String id="2" _locID="2">Cymraeg Application and Network Access Portal</String>", save and close.
    • Copy en-US.xml from /PortalHomePage/Data/Languages to /PortalHomePage/Data/Languages/CustomUpdate and rename the file to cy-UK.xml. Again, open it and change something simple that is easy to spot when the portal is accessed. Example: change "<String id="12" _locID="12">Application and Network Access Portal</String>" to "<String id="12" _locID="12">Cymraeg Application and Network Access Portal</String>". Now go to the bottom of the file and add your custom application strings like this:
    <String id="313" _locID="313">
    <!-- _locID_CDATA="HTM" --><![CDATA[<OL>
                                <LI>To view activity of legacy applications, click <B>Activity</B> on the toolbar.</LI>
                                </OL>]]></String>
    <String id="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="Name_0CF3FC7E9D204ACE8B1A3361D7D779C4">Welsh name</String>
    <String id="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="ShortDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4"> Welsh Application short description</String>
   <String id="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4" locID="LongDesc_0CF3FC7E9D204ACE8B1A3361D7D779C4">Welsh Application long description</String>
</Strings>

                     save and close.

    • Copy the cy-UK.xml you just created in  /PortalHomePage/Data/Languages/CustomUpdate to  /PortalHomePage/Data/Languages.
    • Activate the configuration.

    Important to keep in mind when testing is that the login page (InternalSite) detects the language setting of the connecting browser and tries to match the setting. If the browser has cy-UK as its preffered languange and cy-UK exists in Languages.xml it'll be displayed, otherwise it defaults to en-US. BUT, in order for the portal(PortalHomePage) to display cy-UK.xml there must be a cookie set from the login page. This cookie is NOT automatically set when the login page is loaded, even if the correct language is matched. Without this cookie the portal will default to en-US regardless of the language displayed at login page. To force the UAG to set the cookie, the user must change language(en-US) and then change back to the desired language(cy-UK) at the login page before login.

    I have a fix for that as well  but let's just take one step at the time. Remember to check your xml-files for syntax error before testing(open in IE or something). That usually saves a lot of time :)

    Good Luck Pete! :)

    Regards
    Joakim


    Hi Joakim,

    Can you explain your solution for the language cookie for the portal home page?

    Thanks!