Hi Tikkune,

What I am saying is that if you have your site configured to use only one language, then you don't care if all Dnn's messages are "fixed". See, if you change any messages inside the "core" files, then you leave them as they were before, "fixed", but now saying what you want them to say. If, for example, you wanted your site in localized in spanish, then you would edit those "hard coded" tooltip messages (related to the register form) so that they say "Nombre de Usuario".

The problem arises only if you have more than one locale (language) installed. Because english, for good or bad, is the universal language on the Internet, and a tooltip saying "Usuario" to someone from, say, Japan, looks like Greek ;-)

There are several messages all over DNN that remain "hard coded". The tooltips on the register form are just some of them (most tooltips everywhere else can be localized through the standard resx edition).

To make a long answer short: No, you do not need to install an additional language pack in order to edit the core files. You may edit them as you wish since they are "independent" of all and any of the installed language packs.

Thank you for your other post, I will look into it.

Saludos,
Alejandro.

---

Spanish Language Packs Paquetes de Idioma en Español		English Language Packs Commercial, Professional English

Hi, leupold,

I am relatively new to DNN, so maybe I am wrong. I have posted that the tooltips of each field in the Register Form are fixed and not avilable as Resx resources for localization. Those are the only Tooltips I am referring to, as Tikkune asks specifically about them in this thread (the Register Form's Tooltips).

Unfortunately I did not clarify that all other tooltips are available for localization. Maybe that's what you mean by saying "not true".

If I am wrong about the Register Form's Tooltips, about them being "hard coded", please let me know how to localize them. I am very interested in doing that, since I have recently finished working on a complete spanish language pack (as you did with the German lang. pack), and I couldn't find where to change those strings. I am currently working with DNN v4.5.03.

Thank you for your help!

Saludos,
Alejandro.

PS: One more thing: I didn't know about where to report missing key's localization... I will report all the strings I found I could not localize. Thank you again.

---

Spanish Language Packs Paquetes de Idioma en Español		English Language Packs Commercial, Professional English

The problem with the tooltips is that they were being added to the <a ..> tag using the name of the control, not the actual help text (in PropertyLabelControl.vb):

 Public Property Caption() As String
    Get
        Me.EnsureChildControls()
        Return lblLabel.Text
    End Get
    Set(ByVal Value As String)
        Me.EnsureChildControls()
        lblLabel.Text = Value
        cmdHelp.ToolTip = Value
    End Set
End Property

The solution is to comment this line and add the tooltip to the image in the same way the text is attached to the label and help text:

Public Property ResourceKey() As String
    Get
        Return _ResourceKey
    End Get
    Set(ByVal Value As String)
        _ResourceKey = Value

        Me.EnsureChildControls()

        'Localize the Label and the Help text
        lblHelp.Attributes("resourcekey") = _ResourceKey + ".Help"
        imgHelp.Attributes("resourcekey") = _ResourceKey + ".Help"
        lblLabel.Attributes("resourcekey") = _ResourceKey + ".Text"

    End Set
End Property

Give it a try if you have a moment. I've tested this and seems to solve the problem.

---

Vicenç Masanas
Banyoles, Girona - Spain