Typos in Portuguese Language

Bug #1586375 reported by Ivo Xavier
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
NearBy Scope
Invalid
Undecided
Unassigned
Ubuntu Translations
New
Medium
Ubuntu Portuguese Translators

Bug Description

Hi,

The NearBy scope has some typos in Portuguese from Portugal.

See the attachment.

1) "Actualize" must be replaced by "Atualize". Clean the "c".

2) "Benvindo ao âmbito NearBy" must be replaced by "Bem-vindo ao scope NearBy".

Today Scope was also affected by this typos, but is now fixed: https://bugs.launchpad.net/today-scope/+bug/1517666

Keep the good work :)

Thanks,
Ivo Xavier
Ubuntu Portuguese Translators

Tags: nearby
Revision history for this message
Ivo Xavier (ivoxavier) wrote :
Ivo Xavier (ivoxavier)
description: updated
Changed in ubuntu-translations:
assignee: nobody → Ubuntu Portuguese Translators (ubuntu-l10n-pt)
importance: Undecided → Medium
Changed in ubuntu-translations:
status: New → Opinion
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

@Filipe: Your change of status to "opinion" confuses me. It's intended to be used when there is a difference in opinion between a bug reporter and someone in a position to state that a proposed change should be rejected for some reason, but in that case it should be accompanied by an explanation. Since there is no explanation, I reopen this bug for now.

Changed in ubuntu-translations:
status: Opinion → New
Revision history for this message
Ivo Xavier (ivoxavier) wrote :

I think the typos aren't present in the nearby scope, but in hints scope. Wich is a project that is not present here in launchpad. This type of bug was also present in the today scope(I've posted the link in the description).

Revision history for this message
Filipe André Pinho (pinhoadas) wrote :

@Gunnar: As @Ivo stated above, we can't solve the issue, at least for now. "New" technically means that no one is taking care of this bug. Then, what is the best Status for this situation?

Thx

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Thanks for explaining, Ivo and Filipe. Kind of special situation... Keeping the Ubuntu Translations task open, to keep track of the issue, and invalidate the Nearby Scope task comes to mind.

Sounds like developer involvement is necessary in any case. @Kyle?

(Status "opinion" denotes that no action will be taken, which is why I objected to it.)

Changed in nearby-scope:
status: New → Invalid
Revision history for this message
Kyle Nitzsche (knitzsche) wrote :

Hi all:

Regarding Hints scope not yet being public. We are making the previously unpublic scopes public.

Hints is a special case for the following reason: really, the underlying architecture of having a separate hints scope is not correct. An aggregator scope (made from lp:scope-agggregator, like News, Nearby, Photos, Today, and others) should be able to provide its own hint content. Why? Because such content should always be available (yet is it not available if the hints scope is not installed) AND the content should be correct for the particular version of the agg scope (whereas hints scope cannot provide different content based on agg scope version).

So, the future of the hints scope itself is not 100% certain.

That being said, if we make hints public and translators work on it, and then later the hints scope is killed off, I suppose the translation work would be manually ported to each agg scope so the work would not be lost.

OK I've convinced myself: we should make hints public. :)

Revision history for this message
Filipe André Pinho (pinhoadas) wrote :

@Kyle: When the package is made public, please send us the link to the package to make this process faster.

Thank you!

Revision history for this message
Kyle Nitzsche (knitzsche) wrote :

Hi Filipe: Yes: for every scope I have made public I have sent and announcement on ubuntu-translators list. Also, you can find them here: https://launchpad.net/canonical-scopes

cheers

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.