You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Eduardo Nunes (JIRA)" <ji...@apache.org> on 2012/04/23 02:37:32 UTC
[jira] [Created] (OPENMEETINGS-209) Encoding at install
OpenMeetings
Eduardo Nunes created OPENMEETINGS-209:
------------------------------------------
Summary: Encoding at install OpenMeetings
Key: OPENMEETINGS-209
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-209
Project: Openmeetings
Issue Type: Bug
Components: BuildsAndReleases
Affects Versions: 2.0 Apache Incubator Release
Reporter: Eduardo Nunes
Assignee: SebastianWagner
Priority: Minor
When installing OpenMeetings if you use special character in organization name, this char is not converted ok to database. After install, i have to access organization and change it.
See img attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-209) Encoding at install
OpenMeetings
Posted by "Eduardo Nunes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eduardo Nunes updated OPENMEETINGS-209:
---------------------------------------
Attachment: SNAG-74.jpg
> Encoding at install OpenMeetings
> --------------------------------
>
> Key: OPENMEETINGS-209
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-209
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Eduardo Nunes
> Assignee: SebastianWagner
> Priority: Minor
> Attachments: SNAG-72.jpg, SNAG-74.jpg
>
>
> When installing OpenMeetings if you use special character in organization name, this char is not converted ok to database. After install, i have to access organization and change it.
> See img attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-209) Encoding at install
OpenMeetings
Posted by "SebastianWagner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner resolved OPENMEETINGS-209.
------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0 Apache Incubator Release
> Encoding at install OpenMeetings
> --------------------------------
>
> Key: OPENMEETINGS-209
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-209
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Eduardo Nunes
> Assignee: SebastianWagner
> Priority: Minor
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: SNAG-72.jpg, SNAG-74.jpg
>
>
> When installing OpenMeetings if you use special character in organization name, this char is not converted ok to database. After install, i have to access organization and change it.
> See img attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-209) Encoding at install
OpenMeetings
Posted by "Eduardo Nunes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eduardo Nunes updated OPENMEETINGS-209:
---------------------------------------
Attachment: SNAG-72.jpg
> Encoding at install OpenMeetings
> --------------------------------
>
> Key: OPENMEETINGS-209
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-209
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Eduardo Nunes
> Assignee: SebastianWagner
> Priority: Minor
> Attachments: SNAG-72.jpg
>
>
> When installing OpenMeetings if you use special character in organization name, this char is not converted ok to database. After install, i have to access organization and change it.
> See img attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENMEETINGS-209) Encoding at install
OpenMeetings
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261251#comment-13261251 ]
Maxim Solodovnik commented on OPENMEETINGS-209:
-----------------------------------------------
Hello Sebastian,
Maybe it is better to change page encoding in template file to be UTF-8?
In this case
1) Only 1 line of code will be changed
2) no trascoding will be required
3) All UTF-8 characters will be supported (it is much wider than ISO-8859-1 currently used)
> Encoding at install OpenMeetings
> --------------------------------
>
> Key: OPENMEETINGS-209
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-209
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Eduardo Nunes
> Assignee: SebastianWagner
> Priority: Minor
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: SNAG-72.jpg, SNAG-74.jpg
>
>
> When installing OpenMeetings if you use special character in organization name, this char is not converted ok to database. After install, i have to access organization and change it.
> See img attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENMEETINGS-209) Encoding at install OpenMeetings
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-209.
-----------------------------------------
Assignee: Maxim Solodovnik (was: SebastianWagner)
Closing all old 'Resolved' issues
> Encoding at install OpenMeetings
> --------------------------------
>
> Key: OPENMEETINGS-209
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-209
> Project: Openmeetings
> Issue Type: Bug
> Components: BuildsAndReleases
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Eduardo Nunes
> Assignee: Maxim Solodovnik
> Priority: Minor
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: SNAG-72.jpg, SNAG-74.jpg
>
>
> When installing OpenMeetings if you use special character in organization name, this char is not converted ok to database. After install, i have to access organization and change it.
> See img attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira