mantisbt-lang — MantisBT localization mailing list

Re: [mantisbt-lang] [mantisbt-dev] Mantis 1.1.0rc2 Released

[David A. D. <de...@gn...>]

On Tue, 2007-10-23 at 23:46 -0700, Victor Boctor wrote:
> Hi all,
> 
> Blog Post
> http://www.mantisbt.org/blog/?p=14

You might want to link to the download location, or at least the Mantis
project page, from the blog. 

There's no obvious way to get to there from the blog, other than
striking the /blog/?p=14 portion of the URL, but most people won't
understand that they need to do that to get to the parent project page
to download Mantis. 


-- 
David A. Desrosiers
de...@gn...
se...@gm...
http://projects.plkr.org/
Skype...: 860-967-3820

[mantisbt-lang] Mantis 1.1.0rc2 Released

[Victor B. <vb...@gm...>]

Hi all,

Blog Post
http://www.mantisbt.org/blog/?p=14

Download:
http://www.mantisbt.org/download.php

Regards,
Victor.

Re: [mantisbt-lang] French strings (8859-15 encoded)

[Victor B. <vb...@gm...>]

Supporting all encoding is for backward compatibility.  Such encoding
will be dropped in the future as we know that Mantis users have
upgraded to our UTF 8 only versions and updated their databases.

Till then the updating of the non-UTF8 encoding is useful for such
users but is a secondary priority after the UTF8.

On 10/7/07, Maurice A. LeBlanc <leb...@co...> wrote:
> Francis,
>
> Glad to see you're still active.
>
> On September 29th I had sent the UTF-8 encoded file which Victor
> applied to CVS after correcting an un-escaped apostrophe. That file
> made it into the 1.1.0rc1 release, together with an older version of
> the 8859-15 encoding. On October 4th Victor had requested us to send
> "all encodings of your language (UTF8 is highest priority) within a
> week", so I just updated the 8859-15 file with the changes I had
> previously applied.
>
> Do you know if anything must be done to allow the 8859-15 file to be
> removed without adversely impacting Mantis installation/upgrading?
> >From what I can gather in config_defaults_inc.php the default setting
> is already the UTF-8 file. I suppose we only need to keep the
> strings_french_8859-15 file to support users who may have set
> $g_default_language, $g_language_choices_arr, or $g_fallback_language
> in their config_inc.php configuration file.
>
> Regards,
>
> Maurice
>
>
> ----- Original Message -----
> From: "Francis Labrie" <fra...@sm...>
> To: <man...@li...>
> Sent: Saturday, October 06, 2007 10:20 AM
> Subject: Re: [mantisbt-lang] French strings (8859-15 encoded)
>
>
> Le 05 oct. 2007 =E0 10:56, Maurice A. LeBlanc a =E9crit :
> > Herewith my draft translation of the French strings file with
> > 8859-15
> > encoding.
>
>
> Well, I think we should absolutely drop the ISO-8859-15 encoding for
> french: UTF-8 is clearly better and easier to manage for multiple
> language support. Please use UTF-8 whenever it's possible.
>
>
> --
> Francis Labrie
> Saint-Bruno-de-Montarville, Qu=E9bec, Canada
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> mantisbt-lang mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-lang
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> mantisbt-lang mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-lang
>

Re: [mantisbt-lang] French strings (8859-15 encoded)

[Maurice A. L. <leb...@co...>]

Francis,

Glad to see you're still active.

On September 29th I had sent the UTF-8 encoded file which Victor 
applied to CVS after correcting an un-escaped apostrophe. That file 
made it into the 1.1.0rc1 release, together with an older version of 
the 8859-15 encoding. On October 4th Victor had requested us to send 
"all encodings of your language (UTF8 is highest priority) within a 
week", so I just updated the 8859-15 file with the changes I had 
previously applied.

Do you know if anything must be done to allow the 8859-15 file to be 
removed without adversely impacting Mantis installation/upgrading? 
>From what I can gather in config_defaults_inc.php the default setting 
is already the UTF-8 file. I suppose we only need to keep the 
strings_french_8859-15 file to support users who may have set 
$g_default_language, $g_language_choices_arr, or $g_fallback_language 
in their config_inc.php configuration file.

Regards,

Maurice


----- Original Message ----- 
From: "Francis Labrie" <fra...@sm...>
To: <man...@li...>
Sent: Saturday, October 06, 2007 10:20 AM
Subject: Re: [mantisbt-lang] French strings (8859-15 encoded)


Le 05 oct. 2007 à 10:56, Maurice A. LeBlanc a écrit :
> Herewith my draft translation of the French strings file with 
> 8859-15
> encoding.


Well, I think we should absolutely drop the ISO-8859-15 encoding for
french: UTF-8 is clearly better and easier to manage for multiple
language support. Please use UTF-8 whenever it's possible.


--
Francis Labrie
Saint-Bruno-de-Montarville, Québec, Canada


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a 
browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
mantisbt-lang mailing list
man...@li...
https://lists.sourceforge.net/lists/listinfo/mantisbt-lang

Re: [mantisbt-lang] French strings (8859-15 encoded)

[Francis L. <fra...@sm...>]

Le 05 oct. 2007 =E0 10:56, Maurice A. LeBlanc a =E9crit :
> Herewith my draft translation of the French strings file with 8859-15
> encoding.


Well, I think we should absolutely drop the ISO-8859-15 encoding for =20
french: UTF-8 is clearly better and easier to manage for multiple =20
language support. Please use UTF-8 whenever it's possible.


--
Francis Labrie
Saint-Bruno-de-Montarville, Qu=E9bec, Canada

[mantisbt-lang] French strings (8859-15 encoded)

[Maurice A. L. <leb...@co...>]

Herewith my draft translation of the French strings file with 8859-15 
encoding.

I have added comments to a few lines for further research where the 
functionality was not completely clear to me.

New strings based on the English strings file sent by Victor were 
added to the 1.1 French (8859-15) file distributed with the 1.1.0rc1 
release package.

Regards,

Maurice

Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1

[Victor B. <vb...@gm...>]

Hi Villem,

> Estonian utf-8 texts attached.

This is commited to CVS.

Regards,
Victor

Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1

[Mel L. <wi...@ho...>]

Hi,
Estonian utf-8 texts attached.
Rgds,
Villem

>From: "Victor Boctor" <vb...@gm...>
>Reply-To: man...@li...
>To: "developer discussions" 
><man...@li...>,man...@li...
>Subject: Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1
>Date: Thu, 27 Sep 2007 22:44:35 -0700
>
>Hi all,
>
>I've just refreshed Mantis official bug tracker with the latest code
>that is very close to be 1.1.0rc1 (still planned for the weekend).
>This will allow us to try it in production for a couple of days before
>it is released.  We have fixed several issues in the last couple of
>days and I see no major issues that are still pending.  The following
>issue is almost done and will be checked in before the release:
>
>0007516: My mssql performance tweaks (use of nested queries, affects
>also MySQL and others)
>
>I've attached a zipped copy of the latest English file, so if you
>would like your language to be up-to-date in Mantis 1.1.0rc1, please
>send a zipped update to your localization file asap to mantisbt-lang
>mailing list.
>
>On 9/24/07, Victor Boctor <vb...@gm...> wrote:
> > Hi everyone,
> >
> > Just following up on this issue.  I would like to release 1.1.0rc1
> > next weekend.  I just had a look at the bug tracker and can't see
> > anything major that should stop us from doing so, if any of the
> > developers is keen on the open issues that are currently targetted for
> > 1.1.0, then they can get it in before then, in other words, there are
> > no major open issues.
> >
> > Let us do the final push to get this out.  There are a lot of users
> > that want 1.1.0 gold released so that they can benefit from the huge
> > improvements over 1.0.0.
> >
> > Issues that would be nice to resolve:
> > 0007516: My mssql performance tweaks (use of nested queries, affects
> > also MySQL and others)
> > 0008380: Deleting old user Account results in Database inconsistency
> > 0008336: Require re-login for high impact tasks
> >
> > On 8/21/07, Victor Boctor <vb...@gm...> wrote:
> > > Hi all,
> > >
> > > I am sending this email so that we can identify issues that are
> > > blocking rc1 and issues that are targetted to 1.1 but won't make it in
> > > rc1 (these should be only bug fixes).  Any features that we want to be
> > > in 1.1, should make it in rc1.  Once rc1 is released, the 1.1.0 branch
> > > will be created and all 1.1 fixes will be there.  CVS HEAD will become
> > > Mantis 1.2.
> > >
> > > Following are some issues that are candidates for rc1:
> > >
> > > 1. Tagging (jreese)
> > > 2. Upgrade path to UTF8 via install (thraxisp) - may not make it in
> > > rc1, but should be in 1.1.0.
> > >
> > > We should identify any other issues and update the roadmap to reflect
> > > that.  We should also move the appropriate issues from being targeted
> > > to 1.1.0 to 1.1.0rc1.  This is to have a clear understanding of what
> > > is holding off the rc1 release.
> > >
> > > Ideally, I would like rc1 out of the door by the weekend or early next
> > > week.  I will be on vacation for two weeks following that.
> > >
> > > In the meantime, we should also consider any issues that need to be
> > > fixed for 1.0.9 to be released.  There was some issues pending porting
> > > from the 1.1.x branch.  These were mainly handled by grangeway.
> > >
> > > Regards,
> > > Victor.
> > >
> >


><< strings_english.zip_ >>


>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2005.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


>_______________________________________________
>mantisbt-lang mailing list
>man...@li...
>https://lists.sourceforge.net/lists/listinfo/mantisbt-lang

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

[mantisbt-lang] Now is the time!

[Victor B. <vb...@gm...>]

Hi all,

Since 1.1.0rc1 has just been released, we are approaching the last
chance to implement localization updates.  Please provide send us a
zip file with your localization updates if you want it to be included
in Mantis 1.1.0 gold release.  Note that once we release rc2, we may
decide not to apply any further localization updates to the 1.1.0
branch.

I would appreciate if you send the updates to all encodings of your
language (UTF8 is highest priority) within a week.

Regards,
Victor.

[mantisbt-lang] Mantis 1.1.0rc1 Released

[Victor B. <vb...@gm...>]

Hi everyone,

Are we there yet? Well almost! I've been getting a lot of questions
lately about when 1.1.0 gold will be out. We are almost there, with
the arrival of the rc1 release, we are now in feature freeze and have
already branched the code. Hence, any new development will now go into
1.2.0 code base and the 1.1.0 branch will only get critical bug fixes
and localization updates. This will allow us to quickly reach the
proven stability status and hence be able to release 1.1.0 gold. I am
optimistic that this can happen pretty quick since this rc1 came after
four alpha releases that were deployed in a lot of production sites
including our own official bug tracker.

This release includes features like db2 support, XWiki integration and
tagging. It also has security improvements and some localization
updates. All users of Mantis 1.1.0aX are encouraged to upgrade.

For Mantis instances that use non-latin characterset, there is no
automated upgrade path for data already in the database. Hence, this
wiki page guides you through the upgrade process. Please backup before
you attempt to upgrade. It is also recommended to test the upgrade
process on a backup instance rather than the live one.

See blog for more details:
http://www.mantisbt.org/blog/?p=11

Download:
http://www.mantisbt.org/download.php

Thanks for everyone who contributed to such great release!

Regards,
Victor.

Re: [mantisbt-lang] German translation

[Victor B. <vb...@gm...>]

Hi Martin,

Once you send me the updated zipped language file, I will commit it to CVS.

As for the other encodings, no, I won't be updating them.  If you
provide me with updates versions, I will apply them as is.

On 9/30/07, Martin Fuchs <mar...@gm...> wrote:
> Hello Victor,
>
> first thanks you resolved the issue about "Problem"/"Eintrag" terminology in the german translation by just allowing the user to choose which one he wants to use.
>
> I found a few errors in the current german files and will create an entry in the bug tracker attaching a patch file to correct them.
>
> What is about the old none UTF-localization files like "strings_german_8859-1.txt", will you automatically go through all of them and create them from scratch using the UTF-8 resources?
>
> Regards,
>
>   Martin
>

[mantisbt-lang] German translation

[Martin F. <mar...@gm...>]

Hello Victor,

first thanks you resolved the issue about "Problem"/"Eintrag" terminology in the german translation by just allowing the user to choose which one he wants to use.

I found a few errors in the current german files and will create an entry in the bug tracker attaching a patch file to correct them.

What is about the old none UTF-localization files like "strings_german_8859-1.txt", will you automatically go through all of them and create them from scratch using the UTF-8 resources?

Regards,

  Martin

Re: [mantisbt-lang] French strings

[Victor B. <vb...@gm...>]

Hi Maurice,

This is now applied to CVS.  As I was testing it with
admin/test_langs.php, I've noticed that it includes a syntax error.
The fix is to replace:

$MANTIS_ERROR[ERROR_TAG_NOT_ATTACHED] =3D 'Cette balise n'est pas
associ=C3(c)e =C3  ce bogue.';

with:

$MANTIS_ERROR[ERROR_TAG_NOT_ATTACHED] =3D 'Cette balise n\'est pas
associ=C3(c)e =C3  ce bogue.';

On 9/29/07, Maurice A. LeBlanc <leb...@co...> wrote:
> Herewith my draft translation of the French strings.
>
> I have added comments to a few lines for further research where the
> functionality was not completely clear to me.
>
> New strings based on the English strings file sent by Victor were
> added to the 1.120 French file taken from CVS.
>
> Regards,
>
> Maurice
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mantisbt-lang mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-lang
>
>
>

[mantisbt-lang] French strings

[Maurice A. L. <leb...@co...>]

Herewith my draft translation of the French strings.

I have added comments to a few lines for further research where the 
functionality was not completely clear to me.

New strings based on the English strings file sent by Victor were 
added to the 1.120 French file taken from CVS.

Regards,

Maurice

Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1

[Seiji S. <so...@al...>]

Hi Victor,

> I've attached a zipped copy of the latest English file, so if you
> would like your language to be up-to-date in Mantis 1.1.0rc1, please
> send a zipped update to your localization file asap to mantisbt-lang
> mailing list.

I attached updated Japanese file.
This file includes patch that attached in #7720 "Japanese language
translation patch". So please close #7720.

Regards,
Seiji Sogabe

Re: [mantisbt-lang] Tag, Attach, Detach

[Maurice A. L. <leb...@co...>]

Jorge,

I'm just now adding the new variables to the French language file. 
Pending eventual correction by other French users, I have chosen to 
translate Tag by Balise, Attach by Associer, and Detach by Dissocier.

Regards,

Maurice

PS Victor - I'll be sending an updated file later today.


----- Original Message ----- 
From: "Jorge Andrés Brugger" <li...@da...>
To: "mantisbt-lang" <man...@li...>
Sent: Tuesday, August 28, 2007 9:33 AM
Subject: [mantisbt-lang] Tag, Attach, Detach


Latin-derived languages speakers:

There is a new functionality just added to CVS, tags management. I 
want
to discuss how to translate tag-related terms.

- I´ve translated tag as "Etiqueta". ¿Or should I left it 
untranslated?
(XML "tag" are usually translated as "etiqueta" in tech docs)
- Attach: a tag can be attached to a issue. "Adjuntar" (as attached
files), "Añadir", "Relacionar"? (It´s a bi-directional relationship, a
tag is attached to issue but issue is also attached to tag)
- Detach: My first try was "Separar" but  it doesn't give full sense 
to
detach meaning ... ideas?

Regards

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la 
Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a 
browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
mantisbt-lang mailing list
man...@li...
https://lists.sourceforge.net/lists/listinfo/mantisbt-lang

Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1

[Victor B. <vb...@gm...>]

Hi Jeferson,

> I'm not the official maintainer of the Brazilian translation, but I'm
> sending attached an updated language file that I'm using with 1.1.0rc1-CVS.
>
> If other Brazilian users could (as I've asked before in the message
> "Brazilian Portuguese suggestions to 1.1.0a4") discuss the new
> translations I would appreciate, but if they don't have any opposition,
> and the official maintainer of the Brazilian translation agrees with
> those suggestions, please commit them.

This is now committed to CVS.  Thanks.

Regards,
Victor

Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1

[Jeferson O. <jef...@gm...>]

Victor Boctor wrote:
> I've attached a zipped copy of the latest English file, so if you
> would like your language to be up-to-date in Mantis 1.1.0rc1, please
> send a zipped update to your localization file asap to mantisbt-lang
> mailing list.

Hi Victor,

I'm not the official maintainer of the Brazilian translation, but I'm 
sending attached an updated language file that I'm using with 1.1.0rc1-CVS.

If other Brazilian users could (as I've asked before in the message 
"Brazilian Portuguese suggestions to 1.1.0a4") discuss the new 
translations I would appreciate, but if they don't have any opposition, 
and the official maintainer of the Brazilian translation agrees with 
those suggestions, please commit them.


Regards,

Jeferson Oliveira
Brazil


Sent by Mozilla Thunderbird
http://br.mozdev.org/thunderbird

Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1

[Jeferson O. <jef...@gm...>]

Victor Boctor wrote:
> We have fixed several issues in the last couple of
> days and I see no major issues that are still pending.

The issue "0008397: Localize bug_graph_bystatus" is not a major one, but 
already has a patch. Would be interesting commit it.

Regards,

Jeferson Oliveira
Brazil


Sent by Mozilla Thunderbird
http://br.mozdev.org/thunderbird

Re: [mantisbt-lang] Issues for Mantis 1.1.0rc1

[Victor B. <vb...@gm...>]

Hi all,

I've just refreshed Mantis official bug tracker with the latest code
that is very close to be 1.1.0rc1 (still planned for the weekend).
This will allow us to try it in production for a couple of days before
it is released.  We have fixed several issues in the last couple of
days and I see no major issues that are still pending.  The following
issue is almost done and will be checked in before the release:

0007516: My mssql performance tweaks (use of nested queries, affects
also MySQL and others)

I've attached a zipped copy of the latest English file, so if you
would like your language to be up-to-date in Mantis 1.1.0rc1, please
send a zipped update to your localization file asap to mantisbt-lang
mailing list.

On 9/24/07, Victor Boctor <vb...@gm...> wrote:
> Hi everyone,
>
> Just following up on this issue.  I would like to release 1.1.0rc1
> next weekend.  I just had a look at the bug tracker and can't see
> anything major that should stop us from doing so, if any of the
> developers is keen on the open issues that are currently targetted for
> 1.1.0, then they can get it in before then, in other words, there are
> no major open issues.
>
> Let us do the final push to get this out.  There are a lot of users
> that want 1.1.0 gold released so that they can benefit from the huge
> improvements over 1.0.0.
>
> Issues that would be nice to resolve:
> 0007516: My mssql performance tweaks (use of nested queries, affects
> also MySQL and others)
> 0008380: Deleting old user Account results in Database inconsistency
> 0008336: Require re-login for high impact tasks
>
> On 8/21/07, Victor Boctor <vb...@gm...> wrote:
> > Hi all,
> >
> > I am sending this email so that we can identify issues that are
> > blocking rc1 and issues that are targetted to 1.1 but won't make it in
> > rc1 (these should be only bug fixes).  Any features that we want to be
> > in 1.1, should make it in rc1.  Once rc1 is released, the 1.1.0 branch
> > will be created and all 1.1 fixes will be there.  CVS HEAD will become
> > Mantis 1.2.
> >
> > Following are some issues that are candidates for rc1:
> >
> > 1. Tagging (jreese)
> > 2. Upgrade path to UTF8 via install (thraxisp) - may not make it in
> > rc1, but should be in 1.1.0.
> >
> > We should identify any other issues and update the roadmap to reflect
> > that.  We should also move the appropriate issues from being targeted
> > to 1.1.0 to 1.1.0rc1.  This is to have a clear understanding of what
> > is holding off the rc1 release.
> >
> > Ideally, I would like rc1 out of the door by the weekend or early next
> > week.  I will be on vacation for two weeks following that.
> >
> > In the meantime, we should also consider any issues that need to be
> > fixed for 1.0.9 to be released.  There was some issues pending porting
> > from the 1.1.x branch.  These were mainly handled by grangeway.
> >
> > Regards,
> > Victor.
> >
>

[mantisbt-lang] Brazilian Portuguese suggestions to 1.1.0a4

[Jeferson O. <jef...@gm...>]

Hi Everyone!

I've added the missing new strings to the Brazilian Portuguese 
translation. None of the existing strings was modified.
The attached file has been successfully tested in a Mantis 1.1.0a4 
installation.

I would appreciate if some Brazilian or Portuguese readers Mantis users 
could express your opinion specially about the translations of new 
features like "Roadmap", "Target version" and "Time tracking".

If the official maintainer of the Brazilian translation agrees with 
those suggestions, please commit them.

Below is a list of the new translated strings:

$s_actiongroup_menu_update_target_version = 'Atualizar Previsto para 
Versão';
$s_actiongroup_menu_update_fixed_in_version = 'Atualizar Corrigido na 
Versão';
$s_actiongroup_menu_add_note = 'Adicionar Anotação';

$s_copy_from = 'Copiar De';
$s_copy_to = 'Copiar Para';
$s_copy_versions_from = 'Copiar Versões De';
$s_copy_versions_to = 'Copiar Versões Para';
$s_select_option = '(selecione)';
$s_email_target_version = 'Previsto para a Versão';
$s_balance = 'Saldo';
$s_most_active = 'Mais Ativos';
$s_score = 'Mudanças'; #Dado o contexto, que indica a quantidade de 
alterações realizadas no caso.
$s_all = 'todos';

$s_create_filter_link = 'Criar Link Permanente';
$s_create_short_link = 'Criar Link Reduzido';
$s_filter_permalink = 'O endereço a seguir é um link permanente para o 
filtro atualmente configurado:';

$s_link_custom_field_to_project_title = 'Vincular Campo Personalizado ao 
projeto';
$s_link_custom_field_to_project_button = 'Vincular Campo Personalizado';
$s_linked_projects = 'Projetos Vinculados';

$s_changelog_empty = 'Não há informações disponíveis sobre registros de 
mudanças';
$s_roadmap_link = 'Planejamento';
$s_roadmap = 'Planejamento';
$s_resolved_progress = '%d de %d caso(s) resolvidos. Progresso (%d%%).';
$s_viewing_bug_dependency_graph_title = "Gráfico de Dependências";

$s_time_tracking_billing_link = 'Fatura';
$s_time_tracking = 'Acompanhamento de tempo';
$s_time_tracking_get_info_button = 'Obter informações de acompanhamento 
de tempo';
$s_time_tracking_cost_per_hour = 'Custo / Hora';
$s_time_tracking_cost = 'Custo';
$s_total_time_for_issue = 'Tempo total para o caso = %s';
$s_from_date = 'De';
$s_to_date = 'Até';

$s_access_denied = $MANTIS_ERROR[ERROR_ACCESS_DENIED];

# Twitter Integration
$s_twitter_resolved = "%d: [%s] %s (resolvido por %s em %s)";
$s_twitter_resolved_no_version = "%d: [%s] %s (resolvido por %s)";

# Project Page
$s_development_team = 'Equipe de desenvolvimento';


Any comments upon my work are welcome.


Regards,

Jeferson Oliveira
Brazil


Sent by Mozilla Thunderbird
http://br.mozdev.org/thunderbird

[mantisbt-lang] Tag, Attach, Detach

[<li...@da...>]

Latin-derived languages speakers:

There is a new functionality just added to CVS, tags management. I want 
to discuss how to translate tag-related terms.

- I´ve translated tag as "Etiqueta". ¿Or should I left it untranslated? 
(XML "tag" are usually translated as "etiqueta" in tech docs)
- Attach: a tag can be attached to a issue. "Adjuntar" (as attached 
files), "Añadir", "Relacionar"? (It´s a bi-directional relationship, a 
tag is attached to issue but issue is also attached to tag)
- Detach: My first try was "Separar" but  it doesn't give full sense to 
detach meaning ... ideas?

Regards

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

[mantisbt-lang] Upgrading to Mantis 1.1

[Martin F. <mar...@gm...>]

Hello,

we want to provide a Wiki page describing the required upgrade steps for
an update of an already existing Mantis database to the new Mantis 1.1.x
version. This should handle the issues in using the now by default utilized
UTF8 character encoding. There is already a preliminary version of the
description text, which was mainly from a mail on the Mantis mailing list:

http://www.mantisbt.org/wiki/doku.php/mantisbt:upgrade_to_utf8


The plan is to structure it as a step-by-step guide. Following is a
sample outline proposed by Victor Boctor:

1. What is the issue?
2. Is my installation affected?
3. How to Upgrade?


However there are quite a lot of conditions to take into account:

- Are the contents of the previous database instance already UTF8-encoded?
- Will the new database instance use UTF8 encoding?
- Which encoding is using the PHP installation per default - is it UTF8?
  This affects how the text strings are stored in the current database
  before the migration.
- Will the updated Mantis installation use UTF8-encoded language files
  or not?

So to make the procedure a bit easier - what do you think about an
upgrade path describing a few attempts with/without encoding while
upgrading the database contents? At first the database is backed up,
so that it can be restored after any unsuccessfull try. By providing a
way to look at sufficient test data it would be possible to judge about
the result of each attempt and wether to go on to the next possibility.

Should the description also handle how to procede if the previous
installation already used a 1.1.0x Mantis version - like that one at
www.mantisbt.org? I'd like to say this need not a must, it's enough
to support upgrading from the official stable Mantis releases (1.0.x).


What do you think about this issues regarding the upgrade? Any
comments and contributions to the upgrade description are welcome.


Regards,

     Martin

[mantisbt-lang] Mantis 1.1.0a4 Released

[Victor B. <vb...@gm...>]

Hi Everyone,

This is the fourth alpha release for Mantis 1.1.0. It is likely to be
the last alpha. The next release is planned to be an rc1 release with
which we will branch the code and implement a feature freeze. This
release has more than 100 features and bug fixes including addition of
MantisConnect SOAP API, Twitter integration, permalink filters,
MediaWiki integration, custom relationships, more reporting in summary
page, project info page, 6 security fixes and a lot of other fixes and
improvements. It is a recommended upgrade for all 1.1.0aX
installations.

For Mantis instances that use non-latin characterset, there is no
automated upgrade path for data already in the database.  Hence, the
following wiki page guides you through the upgrade process.  Please
backup before you attempt to upgrade.  It is also recommended to test
the upgrade process on a backup instance rather than the live one.
http://www.mantisbt.org/wiki/doku.php/mantisbt:upgrade_to_utf8

I would like to take this chance to announce three new services:

1. Mantis Blog - http://www.mantisbt.org/blog/
The blog will be used for news and updates relating to new features.
The old news feature on the home page will be phased out and replaced
by the blog.  Users are encouraged to subscribe to the blog news feed.

2. Mantis Twitter - http://twitter.com/mantisbt
Twitter will be used for keeping Mantis users (followers of Mantis
twitter) updated with all issues that are resolved in the bug tracker
and manual updates that are added relating to releases, etc.  If you
have a Twitter account, it is recommend that you follow "mantisbt"
Twitter account.

3. Mantis Job Board - http://mantisbt.edgeio.net/
There is now a Mantis Job Board that allows the Mantis Community to
post and find job posts.  The cost for posting a job is $30 per month.
 The latest jobs also show up on Mantis web pages via the Job Board
widget.

Following are other related services:

Access Mantis from your cell phone / PDA:
http://www.futureware.biz/mantiswap

Access Mantis via Webservice from Java, .NET, Cocoa, and others (the
webservice is now included out-of-the-box with 1.1.0a4, however, the
client libraries will remain hosted by MantisConnect project):
http://www.futureware.biz/mantisconnect

Forums:
http://www.mantisbt.org/forums/

Wiki:
http://www.mantisbt.org/wiki/

Bug Tracker:
http://www.mantisbt.org/bugs/

Mantis Demo:
http://www.futureware.biz/mantisdemo/

Mantis Manual:
http://www.mantisbt.org/manual/

Following is the changelog for this release:

- 0008154: [security] Port: CVE-2007-3215: PHPMailer vulnerability
(thraxisp) - resolved.
- 0008164: [security] Potential URL redirection flaw in
set_project.php (grangeway) - resolved.
- 0008165: [security] Potential URL redirection flaw in
account_prefs_reset.php (grangeway) - resolved.
- 0008166: [security] Potential URL redirection flaw in
permalink_page.php (grangeway) - resolved.
- 0008180: [security] Potential URL redirection flaw in login.php
(grangeway) - resolved.
- 0008181: [security] Display of database error message could be used
to generate Cross site scripting issue (grangeway) - resolved.
- 0007985: [administration] Database Schema that is more up-to-date
than code is reported as out-of-date (vboctor) - resolved.
- 0008094: [administration] Managing versions / release schedule
accross multiple projects. (vboctor) - resolved.
- 0008144: [administration] Remove obsolete CSS edit tool (vboctor) - resolved.
- 0008224: [authentication] anonymous login is not automatic (vboctor)
- resolved.
- 0002950: [bugtracker] Hide Edit or Delete Profile when not needed
(grangeway) - resolved.
- 0002996: [bugtracker] page link from email (in browser) - display
more than "access denied" (grangeway) - resolved.
- 0003477: [bugtracker] print_mantis_error() function does not display
msg. (grangeway) - resolved.
- 0003902: [bugtracker] all logins fail with "Cannot modify header
information" (grangeway) - resolved.
- 0007125: [bugtracker] Application Error #200 (grangeway) - resolved.
- 0007531: [bugtracker] Get a wrong (?) error message by upload a big
file (grangeway) - resolved.
- 0007812: [bugtracker] Remove white box around jump button in main
menu (zakman) - resolved.
- 0007895: [bugtracker] Recently Visited when logged in as Anonymous
shows issues i have not visited (giallu) - resolved.
- 0007928: [bugtracker] print_column_eta function missing (vboctor) - resolved.
- 0007842: [bugtracker] File attachment permissions (giallu) - resolved.
- 0007871: [bugtracker] Move "Add Note" pane below previous notes
(giallu) - resolved.
- 0007984: [bugtracker] Wrong default value for additional info during
report (vboctor) - resolved.
- 0008005: [bugtracker] items cannot be added to projects without
categories (vboctor) - resolved.
- 0008018: [bugtracker] Add configuration option to allow/disallow
free text in platform, os, and os_build (vboctor) - resolved.
- 0008044: [bugtracker] Edit/Delete bugnote buttons missing (giallu) - resolved.
- 0008067: [bugtracker] show status legend on top AND bottom (zakman)
- resolved.
- 0008103: [bugtracker] Cannot modify the bugnote order. (giallu) - resolved.
- 0008111: [bugtracker] No space between date and username in email
notifications (grangeway) - resolved.
- 0008147: [bugtracker] 'continue' while outside loop in function
print_news_string_by_news_id() (grangeway) - resolved.
- 0008150: [bugtracker] Summary By Date could show also resolved bugs
count (giallu) - resolved.
- 0008174: [bugtracker] & is displayed as & stopping us from using
Unicode Characters (grangeway) - resolved.
- 0008190: [bugtracker] Showing Access Level in Note details (giallu)
- resolved.
- 0008195: [bugtracker] Create Project Info Page (vboctor) - resolved.
- 0008208: [bugtracker] Most popular bug table on summary page
(giallu) - resolved.
- 0006633: [change log] Editing a bug in advanced bug update page
(grangeway) - resolved.
- 0008214: [change log] Change Log displays the version description as
many times as the number of issues show (grangeway) - resolved.
- 0008091: [csv] csv_export doesn't work when project name contains
accentuated characters (vboctor) - resolved.
- 0007346: [custom fields] Copy custom fields from one project to
another (zakman) - resolved.
- 0007849: [custom fields] filters on custom date field causes SQL
error (giallu) - resolved.
- 0007981: [custom fields] Manage projects custom field: Link custom
field to project Errors (vboctor) - resolved.
- 0007986: [custom fields] Removing a custom field to project link
from manage_custom_field_edit_page.php returns to wrong page (vboctor)
- resolved.
- 0007987: [custom fields] Projects that a custom field can be linked
to in manage_custom_field_edit_page.php shouldn't include ALL PROJECTS
(vboctor) - resolved.
- 0008002: [custom fields] Unable to report issue. Error "data too
long" on custom field name (grangeway) - resolved.
- 0008121: [custom fields] Error message doesn't show field name after
entering invalid value in custom field (zakman) - resolved.
- 0008047: [db db2] DB2 Support (experimental) (vboctor) - resolved.
- 0005544: [db mssql] MSSQL APPLICATION ERROR 0000401 When Uploading
Files (grangeway) - resolved.
- 0007140: [db mssql] Upload File Less than 8 K (grangeway) - resolved.
- 0007912: [db mssql] Time tracking doesn't work- SQL syntax error
(grangeway) - resolved.
- 0008220: [db mssql] New summary item contains invalid sql (giallu) - resolved.
- 0007417: [documentation] operating mysql user needs DELETE privilege
(grangeway) - resolved.
- 0005138: [email] Bugnote Id doesn't appear in emails (vboctor) - resolved.
- 0007597: [email] Notification e-mail contain no messages.
(grangeway) - resolved.
- 0008016: [email] Check Email broken in 1.1.0a3 (vboctor) - resolved.
- 0008077: [email] Block use of disposable email addresses (vboctor) - resolved.
- 0008176: [email] Email Server offline causes a delay in mantis
interface (grangeway) - resolved.
- 0008101: [feature] List of involved developers (vboctor) - resolved.
- 0006468: [filters] My View page incorrectly sets filters (grangeway)
- resolved.
- 0006725: [filters] Filtering on "duplicate of" fails while "has
duplicate" works (giallu) - resolved.
- 0006836: [filters] Switching to "Advanced Filters" (or "Simple
Filters") forgets the ?filter=N setting (grangeway) - resolved.
- 0007735: [filters] Filters are lost when clicking on page navigation
(vboctor) - resolved.
- 0007982: [filters] "Create Permlink" not reliable (vboctor) - resolved.
- 0007992: [filters] "Create Permalink" should support custom fields
(vboctor) - resolved.
- 0007993: [filters] "Create Permalink" should show URL in a Mantis
page (vboctor) - resolved.
- 0007487: [graphs] wrong title of dependency-graph (grangeway) - resolved.
- 0004831: [installation] accessing mantis webserver through a proxy
websserver (vboctor) - resolved.
- 0007907: [installation] Allow using system adodb (vboctor) - resolved.
- 0008115: [integration] Implement Twitter Integration (vboctor) - resolved.
- 0007733: [ldap] when using LDAP auth blank page upon login if LDAP
extension not loaded (grangeway) - resolved.
- 0006217: [localization] [all lang] Wrong fIlename on download
(vboctor) - resolved.
- 0007681: [localization] [es] Full review of spanish translation
(Bithunter) - resolved.
- 0007730: [localization] [de] Translation change from "Aktualisieren"
to "Bearbeiten" (zakman) - resolved.
- 0007961: [localization] Spanish translation (Bithunter) - resolved.
- 0008023: [localization] [all lang] Wrong URL on summary (vboctor) - resolved.
- 0008031: [localization] Update simplified chinese localization to
1.1.0a3 (giallu) - resolved.
- 0008051: [localization] [all lang] Wrong fIlename on print report
(zakman) - resolved.
- 0008084: [localization] Spelling mistake in value of string
$s_this_bug file lang/strings_spanish.txt (zakman) - resolved.
- 0008113: [localization] Error typo $s_signup_link in Spanish
traslation ..... (zakman) - resolved.
- 0008168: [localization] german localisation in the current
installation at www.mantisbt.org/bug (giallu) - resolved.
- 0008177: [localization] Extra characters in lang/strings_spanish.txt
(giallu) - resolved.
- 0008201: [localization] Sync italian messages (giallu) - resolved.
- 0008221: [localization] Sync italian messages (vboctor) - resolved.
- 0005333: [other] Invalid zip file core/adodb/adodb-time.zip in CVS
(giallu) - resolved.
- 0006772: [other] Bugnote ids are numeric, which is not valid HTML
(giallu) - resolved.
- 0007138: [other] pages are not valid xhtml 1.0 transitional (giallu)
- resolved.
- 0007885: [other] System logging constants (vboctor) - resolved.
- 0008054: [other] Mediawiki integration (vboctor) - resolved.
- 0008138: [other] Add more services to disposable email address
checker (zakman) - resolved.
- 0006773: [relationships] When cloning an issue, cannot make it "not
related" to parent issue (vboctor) - resolved.
- 0007548: [relationships] Status is underlined using a deprecated
HTML element (giallu) - resolved.
- 0008130: [relationships] Custom relationships (grangeway) - resolved.
- 0007947: [roadmap] when bulk assigning target version I get
permission messages (vboctor) - resolved.
- 0008194: [roadmap] Roadmap and Changelog list nesting for
parent/child issues (grangeway) - resolved.
- 0006116: [rss] "Issues" RSS feed doesn't work when
$g_anonymous_account = '' (grangeway) - resolved.
- 0007255: [rss] APPLICATION WARNING #user_get_field() for NO_USER
(grangeway) - resolved.
- 0007938: [rss] Replace non free RSS creation class (vboctor) - resolved.
- 0006063: [scripting] APPLICATION ERROR 0000401 on MSSQL while
uploading files (grangeway) - resolved.
- 0008159: [scripting] Provide MantisConnect webservice out of the box
as the Mantis SOAP API (vboctor) - resolved.
- 0006782: [sql] MantisBT should do "SET NAMES $charset" on connect to
database (vboctor) - resolved.
- 0008215: [sql] APPLICATION ERROR 401 on MySQL with
file_upload_method = DISK (1.1.0a4-CVS) (giallu) - resolved.
- 0007931: [time tracking] $g_time_tracking_hours config option is
never used (davidnewcomb) - resolved.
- 0007944: [time tracking] 'Update Perfs' error in 1.1.0a3 (vboctor) - resolved.
- 0007965: [time tracking] Time tracking information not shown on
email notifications (vboctor) - resolved.
- 0008105: [time tracking] Total time on billing page (vboctor) - resolved.
- 0008131: [upgrade] install/upgrade tries to use "set schema" on a
non db2 installation. (vboctor) - resolved.
- 0007340: [webpage] my view: status percentage legend shown on top
and not as stated (giallu) - resolved.

Regards,
Mantis Team

Re: [mantisbt-lang] [mantisbt-cvs] mantisbt/core database_api.php, 1.60, 1.61

[Victor B. <vb...@gm...>]

Hi Paul,

On 7/25/07, Paul <pa...@qu...> wrote:
> > +     require_once( $t_core_dir . 'gpc_api.php' );
> > +
>
> do we need gpc_api?

I didn't include it in my initial patch but for some reason the user
who tested it told me it was required.  Now that I think about it, it
doesn't make sense since it is in core.php.  Will remove.

> > +                             # @@@ Is there a way to translate any
> charset
> > name to MySQL format? e.g. remote the dashes?
> > +                             # @@@ Is this needed for other databases?
> > +                             if ( strtolower( $c_charset ) === 'utf-8' )
> {
> > +                                     db_query( 'SET NAMES UTF8' );
> > +                             }
>
> Whilst not having thought about this in any great detail, this strikes me as
> being dangerous - in a multiple language environment, are we potentially
> saying that *sometimes* we'll set it for utf-8 but not always depending on
> the user.  I.e. if someone submits a bug in utf8 support and a developer who
> isn't using a utf8 charset then goes to edit the report aren't we going to
> hit potential problems?

I am personally not sure of the impact of setting the encoding of the
connection.  Hence, I went with the option of limiting when this is
called as much as possible.  The hope is that once a Mantis instance
uses UTF8, then it uses it for all languages.  But that is not always
the case.  If you have a suggestion here please let me know.

> > +     # Checks if the database is MySQL
> > +     function db_is_mysql() {
> > +             $t_db_type = config_get( 'db_type' );
> > +
> > +             switch( $t_db_type ) {
> > +                     case 'mysql':
> > +                             return true;
> > +             }
>
> Should this include mysqli ?

Yep, makes sense.  Will add.

> Paul