From: Victor B. <vb...@gm...> - 2006-12-08 09:12:51
|
Hi all, In this alpha release, localization files has been changed to all use the UTF-8 encoding. This allows the use of several languages within the same Mantis instance. The upgrade path to non-English installations is not yet implemented, hence, this alpha release SHOULD ONLY BE USED FOR ENGLISH installations. Among the major updates is the roadmap feature. There has been a database schema changes since 1.1.0a1 release, hence, the install script will need to be executed. Changelog: http://www.mantisbugtracker.com/bugs/changelog_page.php Website: http://www.mantisbugtracker.com Wiki: http://wiki.mantisbugtracker.com Forums: http://forums.mantisbugtracker.com Manual: http://manual.mantisbugtracker.com Blog: http://www.futureware.biz MantisConnect: http://www.futureware.biz/mantisconnect/ MantisWAP: http://www.futureware.biz/mantiswap I would appreciate your feedback on this release, specially with regards to the major new features. Regards, Victor. |
From: Jeferson O. <jef...@gm...> - 2007-02-08 18:45:53
|
"Victor Boctor" escreveu: > The upgrade path to non-English > installations is not yet implemented, hence, this alpha release SHOULD > ONLY BE USED FOR ENGLISH installations. Are there some modifications I can do in my Mantis installation to test the latest version with another language, specially brazilian portuguese? Regards, Jeferson Oliveira Brazil |
From: Juliano F. R. <ml...@ju...> - 2007-02-08 19:12:24
|
Jeferson Oliveira wrote: > Are there some modifications I can do in my Mantis installation to test the > latest version with another language, specially brazilian portuguese? I'm currently maintaining the brazilian portuguese translation of Mantis. The problem with 1.1.0a2 is that the developers are converging all the language character sets to UTF-8, while current installations use different charsets (for example, if you use pt-BR, your installation uses ISO-8859-1 charset). They were developing a database converter to update current installations to UTF-8, but I don't know if it is ready for use. -- Juliano F. Ravasi ·· http://juliano.info/ 5105 46CC B2B7 F0CD 5F47 E740 72CA 54F4 DF37 9E96 "A candle loses nothing by lighting another candle." -- Erin Majors * NOTE: To contact me directly, replace "ml" with "contact" on my e-mail address. * AVISO: Para me contatar diretamente, troque "ml" por "contact" no endereço de e-mail. |
From: Victor B. <vb...@gm...> - 2007-02-08 19:19:52
|
We haven't implemented any conversion solution yet. I would appreciate any help I can get that will do such conversion during installation, specially if it can be done on a DBMS-agnostic way. I would also appreciate if we can test this on other languages and report back what are the effects of installing 1.1.0a2 on non-English languages. I am not very knowledgable in this area, so don't expect me to come up with the solution here. This is a blocking issue for 1.1.0 and we will keep release alpha releases until it's resolved. Once it's resolved we can release an RC release and stable one. On 2/8/07, Juliano F. Ravasi <ml...@ju...> wrote: > Jeferson Oliveira wrote: > > Are there some modifications I can do in my Mantis installation to test= the > > latest version with another language, specially brazilian portuguese? > > I'm currently maintaining the brazilian portuguese translation of Mantis. > > The problem with 1.1.0a2 is that the developers are converging all the > language character sets to UTF-8, while current installations use > different charsets (for example, if you use pt-BR, your installation > uses ISO-8859-1 charset). They were developing a database converter to > update current installations to UTF-8, but I don't know if it is ready > for use. > > -- > Juliano F. Ravasi =B7=B7 http://juliano.info/ > 5105 46CC B2B7 F0CD 5F47 E740 72CA 54F4 DF37 9E96 > > "A candle loses nothing by lighting another candle." > -- Erin Majors > > * NOTE: To contact me directly, replace "ml" with > "contact" on my e-mail address. > > * AVISO: Para me contatar diretamente, troque "ml" > por "contact" no endere=E7o de e-mail. > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job ea= sier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > Mantisbt-lang mailing list > Man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-lang > |
From: Jeferson O. <jef...@gm...> - 2007-02-08 20:08:10
|
Juliano: Thanks for the quick response. Victor: I have tested the version 1.1.0a2 with brazilian portuguese. The only problem I have noticed is the incompatibility with the database charset (latin1 in my installation). Looking for information about how to convert the database charset, I have concluded that is definitely not a pleasant task, but I'll try do it as soon as possible and post the results here. Jeferson Oliveira Brazil |
From: Victor B. <vb...@gm...> - 2007-02-09 00:29:49
|
On 2/8/07, Jeferson Oliveira <jef...@gm...> wrote: > Juliano: > Thanks for the quick response. > > Victor: > I have tested the version 1.1.0a2 with brazilian portuguese. The only > problem I have noticed is the incompatibility with the database charset > (latin1 in my installation). Looking for information about how to convert > the database charset, I have concluded that is definitely not a pleasant > task, but I'll try do it as soon as possible and post the results here. Thanks Jeferson, looking forward to hear from you. Regards, Victor |
From: Jeferson O. <jef...@gm...> - 2007-02-11 04:51:27
|
After some hours trying to convert my Mantis database to utf-8 I now have a Mantis 1.1.0a2 installation compatible with the database. :D It wasn't an easy task. So let me tell you the steps I did: - I was running MySQL 4.0, that doesn't support UTF-8 charset, so I did a backup of the database, removed the old version and installed MySQL 5.0.18 (I think version 4.1 would be enough), that comes with UTF-8 as the default server charset; - I tried a lot of ways to convert the data to UTF-8, including the steps recommended and the first method really efficient I found was open the dumped file in UltraEdit and use its conversion tools to change the file contents charset (File/Conversions/ASCII to UTF-8 (Unicode Editing)) :-) - Looking for something more automatic, I decided to search for help at Google, and found an article (http://climbtothestars.org/archives/2004/07/18/converting-mysql-database-contents-to-utf-8/) in which the author uses the iconv library (http://www.gnu.org/software/libiconv) to convert the file contents. - After download and install iconv, then I created a new db: CREATE DATABASE `bugtracker` DEFAULT CHARACTER SET utf8 - converted the file contents using iconv: iconv -f latin1 -t utf-8 backup_latin1.sql > backup_utf8.sql - and imported the contents of the converted file into the new database: mysql -uUser -pPassword bugtracker < backup_utf8.sql Maybe Mantis, to do this conversion automatically, could use the iconv php extension, as used by phpmyadmin in its charset conversion library ("libraries\charset_conversion.lib.php"). Regards, Jeferson Oliveira Brazil |
From: Jeferson O. <jef...@gm...> - 2007-02-11 04:58:28
|
Jeferson Oliveira escreveu: > including the steps recommended ... in the MySQL manual related sections: http://dev.mysql.com/doc/refman/5.1/en/charset-conversion.html |