Hi Suelane,
The images you sent through (screen shots) are too small to be able to read any of the text. Could you please send us larger versions of those files (full size if possible). The GBIF list may be processing or blocking large attachments so could also CC us directly via the email address: support@ala.org.au?
Regards
Nick -- Nick dos Remedios Atlas of Living Australia http://www.ala.org.au/
From: "Suelane G. Fontes" <suelane@uol.com.brmailto:suelane@uol.com.br> Date: Tuesday, 1 April 2014 4:25 am To: "ala-portal@lists.gbif.orgmailto:ala-portal@lists.gbif.org" <ala-portal@lists.gbif.orgmailto:ala-portal@lists.gbif.org> Cc: "silvio.stanzani@gmail.commailto:silvio.stanzani@gmail.com" <silvio.stanzani@gmail.commailto:silvio.stanzani@gmail.com> 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@uol.com.brmailto:suelane@uol.com.br
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 alatag:occurrenceTableRow tag and then adding a prefix to the fieldName parameter so that your i18n properties are grouped.
<div id="additionalProperties"> <h3>Additional properties</h3> <table class="occurrenceTable table table-bordered table-striped table-condensed" id="miscellaneousPropertiesTable"> <!-- Higher Geography --> <c:forEach items="${record.raw.miscProperties}" var="entry"> <alatag:occurrenceTableRow annotate="true" section="geospatial" fieldCode="${entry.key}" fieldName="field.${entry.key}" fieldNameIsMsgCode="true">${entry.value}</alatag:occurrenceTableRow> </c:forEach> </table> </div>
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@uol.com.brmailto:suelane@uol.com.br> Date: Tuesday, 1 April 2014 4:25 am To: "ala-portal@lists.gbif.orgmailto:ala-portal@lists.gbif.org" <ala-portal@lists.gbif.orgmailto:ala-portal@lists.gbif.org> Cc: "silvio.stanzani@gmail.commailto:silvio.stanzani@gmail.com" <silvio.stanzani@gmail.commailto:silvio.stanzani@gmail.com> 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@uol.com.brmailto:suelane@uol.com.br
Hi Nick, How are you?
About the second and third points of your e-mail, We don
2014-04-02 2:56 GMT-03:00 Nick.Dosremedios@csiro.au:
Hi Suelane,
- 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 alatag:occurrenceTableRow tag and then adding a prefix to the fieldName parameter so that your i18n properties are grouped.
<div id="additionalProperties"> <h3>Additional properties</h3> <table class="occurrenceTable table table-bordered table-stripedtable-condensed" id="miscellaneousPropertiesTable"> <!-- Higher Geography --> <c:forEach items="${record.raw.miscProperties}" var="entry"> <alatag:occurrenceTableRow annotate="true" section="geospatial" fieldCode="${entry.key}" fieldName="field.${entry.key}" fieldNameIsMsgCode="true"> ${entry.value}</alatag:occurrenceTableRow> </c:forEach> </table> </div>
- 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.
- 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.
- 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@uol.com.br Date: Tuesday, 1 April 2014 4:25 am To: "ala-portal@lists.gbif.org" ala-portal@lists.gbif.org Cc: "silvio.stanzani@gmail.com" silvio.stanzani@gmail.com Subject: [Ala-portal] internationalization problems
Hi,
We are developing the Portuguese version of ALA portal using the internationalization
mechanisms provided by ALA.
- 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?
- Where can I find the terms which appears in the combo box
“environmental layer”? such combo
is shown in figure 2:
- In the advanced research tab there are fields which we could not find,
as shown in figure 3.
Where should I found such terms?
- 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@uol.com.br
Ala-portal mailing list Ala-portal@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ala-portal
Sorry for my last email. I sent it by mistake.
Hi Nick,
I would like to comment about the second and third points of your email. We don't want reuse the environmental layers and regions data of Australia. We think these software features are awesome and it will be essentials in the Brazilian Atlas. We would like to deeply understand this feature and customize them with our data. We have many environmental layers and regions of Brazil that we would like to put in the Atlas.
So if you have additional documentation about these features that can be shared with us, we would like to receive them. At this moment we are initiating activities to understand the Spatial Portal and the Regions feature. We have great interest in these features.
Thanks again.
Regards,
Daniel Lins da Silva (Mobile) 55 11 96144-4050 Research Center on Biodiversity and Computing (Biocomp) University of Sao Paulo, Brazil daniellins@usp.br daniel.lins@gmail.com
2014-04-02 10:59 GMT-03:00 Daniel Lins daniel.lins@gmail.com:
Hi Nick, How are you?
About the second and third points of your e-mail, We don
2014-04-02 2:56 GMT-03:00 Nick.Dosremedios@csiro.au:
Hi Suelane,
- 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 alatag:occurrenceTableRow tag and then adding a prefix to the fieldName parameter so that your i18n properties are grouped.
<div id="additionalProperties"> <h3>Additional properties</h3> <table class="occurrenceTable table table-bordered table-stripedtable-condensed" id="miscellaneousPropertiesTable"> <!-- Higher Geography --> <c:forEach items="${record.raw.miscProperties}" var="entry"> <alatag:occurrenceTableRow annotate="true" section="geospatial" fieldCode="${entry.key}" fieldName="field.${entry.key}" fieldNameIsMsgCode="true"> ${entry.value}</alatag:occurrenceTableRow> </c:forEach> </table> </div>
- 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.
- 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.
- 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@uol.com.br Date: Tuesday, 1 April 2014 4:25 am To: "ala-portal@lists.gbif.org" ala-portal@lists.gbif.org Cc: "silvio.stanzani@gmail.com" silvio.stanzani@gmail.com Subject: [Ala-portal] internationalization problems
Hi,
We are developing the Portuguese version of ALA portal using the internationalization
mechanisms provided by ALA.
- 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?
- Where can I find the terms which appears in the combo box
“environmental layer”? such combo
is shown in figure 2:
- In the advanced research tab there are fields which we could not find,
as shown in figure 3.
Where should I found such terms?
- After the internationalization process a number of codificationerrors 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@uol.com.br
Ala-portal mailing list Ala-portal@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ala-portal
-- Daniel Lins da Silva (Cel) 11 6144-4050 daniel.lins@gmail.com
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@uol.com.br] Sent: Tuesday, 8 April 2014 4:50 AM To: dos Remedios, Nick (CES, Black Mountain) Cc: silvio.stanzani@gmail.com; suelane@uol.com.br; ala-portal@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@csiro.au Enviada: Quarta-feira, 2 de Abril de 2014 05:56 Para: suelane@uol.com.br,ala-portal@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@uol.com.br<UrlBlockedError.aspx>> Date: Tuesday, 1 April 2014 4:25 am To: "ala-portal@lists.gbif.org<UrlBlockedError.aspx>" <ala-portal@lists.gbif.org<UrlBlockedError.aspx>> Cc: "silvio.stanzani@gmail.com<UrlBlockedError.aspx>" <silvio.stanzani@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@uol.com.br<UrlBlockedError.aspx>
Hi Nick,
I'm sending the compressed file as requested. I also renamed the file extension from .zip to .xxx.
Let me know if you still have problems.
Thank you!
Regards,
Daniel Lins
Em 7 de abril de 2014 15:50, Suelane G. Fontes suelane@uol.com.brescreveu:
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@csiro.au *Enviada:* Quarta-feira, 2 de Abril de 2014 05:56 *Para:* suelane@uol.com.br,ala-portal@lists.gbif.org *Assunto:* [Ala-portal] internationalization problems
Hi Suelane,
- 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}
- 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.
- 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.
- 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@uol.com.brhttp://../../../undefined/compose?to=suelane@uol.com.br
Date: Tuesday, 1 April 2014 4:25 am To: "ala-portal@lists.gbif.orghttp://../../../undefined/compose?to=ala-portal@lists.gbif.org" <ala-portal@lists.gbif.orghttp://../../../undefined/compose?to=ala-portal@lists.gbif.org
Cc: "silvio.stanzani@gmail.comhttp://../../../undefined/compose?to=silvio.stanzani@gmail.com" <silvio.stanzani@gmail.comhttp://../../../undefined/compose?to=silvio.stanzani@gmail.com
Subject: [Ala-portal] internationalization problems
Hi,
We are developing the Portuguese version of ALA portal using the internationalization
mechanisms provided by ALA.
- 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?
- Where can I find the terms which appears in the combo box
“environmental layer”? such combo
is shown in figure 2:
- In the advanced research tab there are fields which we could not find,
as shown in figure 3.
Where should I found such terms?
- 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@uol.com.brhttp://../../../undefined/compose?to=suelane@uol.com.br
Ala-portal mailing list Ala-portal@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ala-portal
Hi Daniel and Suelane,
I’ve had a look at your messages_es.properties file and it appears to contain text which has been encoded in a mixture of UTF-8 and Western (Windows-1252). When I view the file in a text editor that lets me change the character encoding (you can use a web browser to do this too), I can read some of the file properly with UTF-8 and other parts of the file with the encoding set to Western (Windows-1252). So I think this file has been edited on a number of occasions, possibly on different computers and this has resulted in a mixture of the 2 character encodings.
Nick dos Remedios Atlas of Living Australia http://www.ala.org.au/
From: Daniel Lins <daniel.lins@gmail.commailto:daniel.lins@gmail.com> Date: Wednesday, 9 April 2014 12:07 pm To: "Suelane G. Fontes" <suelane@uol.com.brmailto:suelane@uol.com.br> Cc: Nick <nick.dosremedios@csiro.aumailto:nick.dosremedios@csiro.au>, Silvio Stanzani <silvio.stanzani@gmail.commailto:silvio.stanzani@gmail.com>, "ala-portal@lists.gbif.orgmailto:ala-portal@lists.gbif.org" <ala-portal@lists.gbif.orgmailto:ala-portal@lists.gbif.org> Subject: Re: [Ala-portal] internationalization problems
Hi Nick,
I'm sending the compressed file as requested. I also renamed the file extension from .zip to .xxx.
Let me know if you still have problems.
Thank you!
Regards,
Daniel Lins
Em 7 de abril de 2014 15:50, Suelane G. Fontes <suelane@uol.com.brmailto:suelane@uol.com.br> escreveu: 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@csiro.aumailto:Nick.Dosremedios@csiro.au Enviada: Quarta-feira, 2 de Abril de 2014 05:56 Para: suelane@uol.com.brmailto:suelane@uol.com.br,ala-portal@lists.gbif.orgmailto:ala-portal@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@uol.com.brhttp://../../../undefined/compose?to=suelane@uol.com.br> Date: Tuesday, 1 April 2014 4:25 am To: "ala-portal@lists.gbif.orghttp://../../../undefined/compose?to=ala-portal@lists.gbif.org" <ala-portal@lists.gbif.orghttp://../../../undefined/compose?to=ala-portal@lists.gbif.org> Cc: "silvio.stanzani@gmail.comhttp://../../../undefined/compose?to=silvio.stanzani@gmail.com" <silvio.stanzani@gmail.comhttp://../../../undefined/compose?to=silvio.stanzani@gmail.com> 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-8170tel:55%2011%2099514-8170 Research Center on Biodiversity and Computing (Biocomp) University of Sao Paulo, Brazil suelane@uol.com.brhttp://../../../undefined/compose?to=suelane@uol.com.br
_______________________________________________ Ala-portal mailing list Ala-portal@lists.gbif.orgmailto:Ala-portal@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ala-portal
-- Daniel Lins da Silva (Cel) 11 6144-4050 daniel.lins@gmail.commailto:daniel.lins@gmail.com
participants (3)
-
Daniel Lins -
Nick.Dosremedios＠csiro.au -
Suelane G. Fontes