[Ala-portal] internationalization problems

[Nick.Dosremedios at csiro.au]

Hi Suelane,

Our email server blocked the .JSP attachment from your email (McAfee Security thinks its malware). I've been advised that you need to put it inside a ZIP file and resend it that way. Are you able to do this and send it again please?

Nick
--
Nick dos Remedios
Atlas of Living Australia
Tel. (61 2) 6246 4434
CSIRO Ecosystem Sciences
GPO Box 1700
Canberra ACT 2601, Australia
http://www.ala.org.au/
________________________________
From: Suelane G. Fontes [suelane at uol.com.br]
Sent: Tuesday, 8 April 2014 4:50 AM
To: dos Remedios, Nick (CES, Black Mountain)
Cc: silvio.stanzani at gmail.com; suelane at uol.com.br; ala-portal at lists.gbif.org
Subject: Re: [Ala-portal] internationalization problems

Hi Nick!

The problem 1, is solved. The solution that you passed me did suit my needs perfectly!
The problem 4, how you did suggestion ... I am sending the files (recordCoreDiv.jsp and messages_pt_BR.properties) to you to test.

Thank you!

Regards.


________________________________

De: Nick.Dosremedios at csiro.au
Enviada: Quarta-feira, 2 de Abril de 2014 05:56
Para: suelane at uol.com.br,ala-portal at lists.gbif.org
Assunto: [Ala-portal] internationalization problems

Hi Suelane,

1) I think you are asking about the properties in Figure 1 listed under “Propriedades Adicionais”, is that correct (the fields you mentioned do not appear to be listed in your example - figure 1)?
I think this can be done by adding the optional parameter fieldNameIsMsgCode to the  tag and then adding a prefix to the fieldName parameter so that your i18n properties are grouped.




Additional properties



                fieldName="field.${entry.key}" fieldNameIsMsgCode="true">${entry.value}




2) I’m afraid we are planning to remove the “environmental layers” feature, as it is heavily tied to the ALA spatial portal and the layers provided are licensed to ALA only.

3) I’m not clear on which fields you could not find in Figure 3. If you are referring to the “regions” section (IBRA, IMCRA and LGA fields), then I would suggest that these be removed as they are specific to Australia only.

4) I’m not sure why the special characters are not displaying correctly. I would check the character encoding for your messages_XX.properties files to make sure they are encoded in UTF-8. If you could send me your messages_pt_BR.proerties file (and one of the JSP files you have changed (e.g showCore.jsp) I could test it here as well.

Regards

Nick

From: "Suelane G. Fontes" <suelane at uol.com.br<UrlBlockedError.aspx>>
Date: Tuesday, 1 April 2014 4:25 am
To: "ala-portal at lists.gbif.org<UrlBlockedError.aspx>" <ala-portal at lists.gbif.org<UrlBlockedError.aspx>>
Cc: "silvio.stanzani at gmail.com<UrlBlockedError.aspx>" <silvio.stanzani at gmail.com<UrlBlockedError.aspx>>
Subject: [Ala-portal] internationalization problems

 Hi,
We are developing the Portuguese version of ALA portal using the internationalization
mechanisms provided by ALA.
1) We provided translation for the “view register” functionality as shown in figure 1.
Most terms were found in “recordCoreDiv.jsp” file, but terms such as Data provider name,
Data provider uid, Institution uid And so on, could no be found in that file. Where is the right
 location to find such terms?
2) Where can I find the terms which appears in the combo box “environmental layer”? such combo
is shown in figure 2:
3) In the advanced research tab there are fields which we could not find, as shown in figure 3.
Where should I found such terms?
4) After the internationalization process a number of codification errors appeared as shown in
figure 4. How can I set the correct codification in ALA Portal in order to properly show the
Portuguese characters, such as: ~, ` and ´ .
The figures were uploaded as attachments.
Thanks.
Regards.
_________________________________________________
Suelane Garcia Fontes
(Cel) 55 11 99514-8170
Research Center on Biodiversity and Computing (Biocomp)
University of Sao Paulo, Brazil
suelane at uol.com.br<UrlBlockedError.aspx>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gbif.org/pipermail/ala-portal/attachments/20140409/4a958a58/attachment.html