Mono Support How to change LoginText and LogoutText 

Viewed 26994 time(s), 7 post(s), 9/25/2012 11:18:04 AM - by GeorgeBirbilis7
9/25/2012 11:18:04 AM
0 Reputation 1 Total posts

in Login.aspx there is

<asp:PlaceHolder ID="panStatus" runat="server">
<asp:LinkButton runat="server" ID="btnButton"><%= LogoutText %></asp:LinkButton>
<asp:HyperLink runat="server" ID="btnLink"><%= LoginText %></asp:HyperLink>
</asp:PlaceHolder>

1) how can one change LoginText and LogoutText? Are they in some site setting or does one have to use localization facility for that?

2) Speaking of localization facility, does it support FALLBACK? That is if something isn't localized to a certain language does it fallback to the english one? Also can one use the localization facility to edit the default language strings too (assuming this will affect the fallback too)

1
9/25/2012 11:57:18 AM
15993 Reputation 2214 Total posts

Hi,

you can change the Login & Logout labels. There are two ways you can do this, if you are going to use resx resources inside the Visual Studio then you have Localization solution inside the MonoX package that you can use to translate the resources (everything is done inside the VS and solution needs to be compiled and deployed). If you want you can change resource provider to database provider and then use the UI in MonoX administration to change the resources.

Both providers support fallback and yes, you can edit default language and is should fallback to changed resource.

Regards

2
9/25/2012 10:32:50 PM
0 Reputation 3 Total posts

There's a thing with the localization that troubles me. Suppose I localize MonoX and then there's a new version out. Won't I need some diff tool to get my changes (calculated by the tool from the resources I had localized) and use some merge functionality to merge them later on into the newer build's resources? (or have some "translation memory" facility that can remember the pairs of original text and localized text and suggest them where appropriate when working on a future monox build's resources)

I don't think Visual Studio has such tool. Think Amanuens had such tools online but unfortunately they're discontinuing that nice online service.

Given that resx is XML one could use some XML Diff/Merge tool from Altova or something, but not sure if there's any freeware one or even any free tools specialized on resx localization.

3
9/25/2012 10:44:15 PM
0 Reputation 3 Total posts

BTW, Google has a very nice facility where you can get automatic translation on your site and also manage those translations overriding default ones and moderating end-user translation suggestions for your site (crowdsourced automatic translation fine-tuning that is). Also admin can invite editors (stakeholders / language - field experts) to edit the default translations.

I believe MonoX should provide easy way to integrate that Google widget at one's site.

https://translate.google.com/manager/

"Key features
- Instantly translate your website into 60+ languages using Google's Translate
- Customize and improve the translation of your website
- Collect and use translation suggestions from your users
- Invite editors to manage translations and suggestions"

4
9/25/2012 10:51:03 PM
0 Reputation 3 Total posts

There's a bug at Google's Translation Manager page, if you go to
http://translate.google.com/manager/?hl=en
then the button "Add to your website now" works, else it throws HTTP 500 Internal Server Error if the URL misses the /?hl=en suffix

5
10/5/2012 9:11:16 AM
15993 Reputation 2214 Total posts

Hi,

updating localization resources is never ending problem, there are few approaches that you may take but neither of them are bullet proof. Some of our clients use source control software in combination with WinMerge so they can track changes made to resource files and decide if they should merge, delete or amend something. Another approach would be to use different resource files for your custom development. Or you can use DB resource provider and track changes via MonoX change scripts (a bit tedious approach if you are developer).

There's a thing with the localization that troubles me. Suppose I localize MonoX and then there's a new version out. Won't I need some diff tool to get my changes (calculated by the tool from the resources I had localized) and use some merge functionality to merge them later on into the newer build's resources? (or have some "translation memory" facility that can remember the pairs of original text and localized text and suggest them where appropriate when working on a future monox build's resources)
Google Translation manager is a great tool but I'm not sure that it can fit the MonoX purposes as there are too so much dynamic content that is generated by the modules. e.g. it will translate blog articles. That aside I'm not sure how easy would be to track the changes, your web app will depend on the Google service etc.

Regards

6
4/15/2013 2:46:34 PM
2793 Reputation 345 Total posts

For completness, since Google has changed URL, the correct URL to add a site to that service I mentioned above is:
https://translate.google.com/manager/website/add?hl=en
still seems to have that ugly bug that if ?hl=en is mising from their URLs it fails (e.g. the add website button)

7
This is a demo site for MonoX. Please visit Mono Software for more info.