I see that several of the property values have a trailing tilda ( ~ ).
Is that intentional?
Not intentional. I forgot to remove them. I'm removing as I go moving
forward in translation process.
:-)
____________________________
Rafael Torres Coelho Soares
rafaelcba(a)gmail.com
http://rafaeltuelho.wordpress.com
Brasília - DF - Brasil
On Thu, Jun 2, 2011 at 10:47, Jay Shaughnessy <jshaughn(a)redhat.com> wrote:
>
> I'm not sure why that is happening. I'm using Eclipse 3.5 so perhaps
> it's a compatibility issue with the older eclipse version. It is still
> a valid format so I guess we can ignore that formatting glitch. Or,
> perhaps moving forward we'll change to aligning the equal sign and maybe
> the problem will go away. We need to use conventions that minimize
> formatting changes when IJ users and Eclipse users both work on the files.
I see that several of the property values have a trailing tilda ( ~ ).
Is that intentional?
>
> On 6/1/2011 10:53 PM, Rafael Soares wrote:
> > Hello Jay. This plugin is very cool! I didn't know it.
> >
> > I'm translating the pt/pt-BR bundle. I installed the Plugin on my
> > Eclipse (JBDS 3.0.1.GA <
http://3.0.1.GA>), configured it as you
> > mentioned in Wiki Page. But when I save the bundle It still align some
> > '=' signs on its left side.
> >
> > The strange is that the 'ResourceBundle Editor' do this only on some
> > blocks and only on left side of '=' signs. See a piece of my bundle:
> >
> > view_resource_monitor_table_max = Maximum
> > view_resource_monitor_table_min = Minimum
> > view_resource_title_component_errors_tooltip = Shows managed component
> > errors. Click for details~
> > view_resource_title_tagUpdateFailed = Failed to update resource tags~
> > view_searchBar_defaultPattern = definir nome para o padr\u00E3o
> > view_searchBar_error_selectSavedSearch = ''Erro ao selecionar a
> pesquisa''
> > view_searchBar_query = Pesquisa
> > view_searchBar_resourceGroups = Grupos de Recursos
> > view_searchBar_resources = Recursos
> > view_searchBar_welcomeMessage = procurar por {0}s
> > view_searchGUI_loginStatus = Imposs\u00EDvel determinar o status
> > do login, verifique o status do servidor~
> > view_selector_assigned = Associado {0}
> > view_selector_available = Dispon\u00EDvel {0}
> > view_subTab_error_disabled = N\u00E3o \u00E9 poss\u00EDvel
> > selecionar uma subTab desabilidada [{0}].
> > view_summaryDashboard_resetConfirm = Reset to default summary
> > dashboard (lose local changes)?
> > view_summaryOverviewForm_error_descriptionChangeFailure = Failed to
> > change description of Resource with id {0} from [{1}] to [{2}].~
> > view_summaryOverviewForm_error_locationChangeFailure = Failed to
> > change location of Resource with id {0} from [{1}] to [{2}].~
> > view_summaryOverviewForm_error_nameChangeFailure = Failed to change
> > name of Resource with id {0} from [{1}] to [{2}].~
> > view_summaryOverviewForm_error_traitsLoadFailure = Failed to load
> > traits for {0}.~
> > view_summaryOverviewForm_field_description = Description~
> >
> > Regards.
> > ____________________________
> > Rafael Torres Coelho Soares
> > rafaelcba(a)gmail.com <mailto:rafaelcba@gmail.com>
> >
http://rafaeltuelho.wordpress.com
> > Brasília - DF - Brasil
> >
> >
> > On Wed, Jun 1, 2011 at 12:53, Jay Shaughnessy <jshaughn(a)redhat.com
> > <mailto:jshaughn@redhat.com>> wrote:
> >
> >
> > Update: Moving forward with the recommended approach mentioned in
> the
> > wiki. As such I've removed the (now obsolete) section comments
> > from the
> > properties files. The properties are organized by the IDE plugins
> > (alphabetical when manipulated by eclipse). New properties in the
> > default bundle are copied into the locale bundles and commented out.
> > Updated messages in the default bundle will have the updated text
> > copied
> > to the locale bundles and will then be commented out. So, translators
> > need only search for commented lines to find messages needing
> > translation.
> >
> >
http://rhq-project.org/display/RHQ/Working+with+the+Resource+Bundles
> >
> >
> > On 5/31/2011 10:26 AM, Jay Shaughnessy wrote:
> > > This is relevant for anyone writing GUI code or performing
> > localization.
> > >
> > > Last Friday I wanted to add and remove some messages while
> > working on
> > > the resource factory wizard (for creating child resources). I
> > quickly
> > > realized that folks out there have been doing localization
> (thanks!)
> > > because there are now several local-specific files.
> > >
> > > This of course makes it more challenging to add/remove/change
> > properties
> > > as each file needs to be touched. So, after a little searching
> > I found
> > > an Eclipse plugin that does just what I wanted, manages all the
> > resource
> > > bundles through a special Eclipse UI. I used this and quickly
> > made the
> > > changes I wanted.
> > >
> > > But there was a catch, and I should have seen it coming. The
> > IDE plugin
> > > basically now manages the underlying resource bundle files. After
> > > committing the changes to Git I realized that it had reordered
> > the files
> > > (alphabetically). This completely throws off the previous
> > structure
> > > of the file and the existing comment placement.
> > >
> > > Instead of reverting I've decided to promote the change and
> > would like
> > > to solicit feedback. I think moving forward it will be much
> > easier to
> > > use the IDE plugins for resource bundle handling. And I know that
> > > IntelliJ also has a resource bundle feature/plugin. I've
> > started a wiki
> > > page for this, to discuss the different IDE setup and to collect
> > > conventions for working on the resource bundles. It's here:
> > >
> > >
>
http://rhq-project.org/display/RHQ/Working+with+the+Resource+Bundles
> > >
> > > In short, working with the plugin makes it much easier to manage
> the
> > > several files in play, to locate undefined properties, and to
> > quickly
> > > compare the default to the localized strings. The alphabetical
> > > structure is actually better, I think, even when inspecting the
> > files
> > > outside of the plugin view, because the hierarchical property names
> > > provide structure already. In fact, the plugin can give you a
> > tree view
> > > using that structure.
> > >
> > > So, I propose from this point forward the resource bundles be
> > > manipulated only (at least by devs, if not localizers as well) via
> > > Eclipse or IJ resource bundle plugins. Please let me know your
> > thoughts
> > > and/or proposed conventions. Thanks, Jay
> > >
> > > _______________________________________________
> > > rhq-devel mailing list
> > > rhq-devel(a)lists.fedorahosted.org
> > <mailto:rhq-devel@lists.fedorahosted.org>
> > >
https://fedorahosted.org/mailman/listinfo/rhq-devel
> > >
> > _______________________________________________
> > rhq-devel mailing list
> > rhq-devel(a)lists.fedorahosted.org
> > <mailto:rhq-devel@lists.fedorahosted.org>
> >
https://fedorahosted.org/mailman/listinfo/rhq-devel
> >
> >
> >
> > _______________________________________________
> > rhq-devel mailing list
> > rhq-devel(a)lists.fedorahosted.org
> >
https://fedorahosted.org/mailman/listinfo/rhq-devel
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/rhq-devel
>