uniform comma below characters for romanian translations

Bug #230725 reported by Adi Roiban
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I don't know if you know this problem so I will describe it.

The Romanian standard characters are S with comman below and T with comma below and it is implemented in GNU/Linux and MacOS.
In the past many fonts does not had this character and the cedilla version was used instead. Also not all fonts from Windows XP are shiped with comma below.
This is why Romanian translations used a mixture of comma below and cedilla characters.

It would be great if when a user tries to add a string for romanian containing cedilla it will be replaced with comma below version (the standard version). This happens very often when translations are made from Windows XP.

Do you think you can help us in having correct comma below characters in Launchpad?

Revision history for this message
Adi Roiban (adiroiban) wrote :

There are four conversions

First:
from U+015E LATIN CAPITAL LETTER S WITH CEDILLA
to U+0218 LATIN CAPITAL LETTER S WITH COMMA BELOW

Second:
from U+015F LATIN SMALL LETTER S WITH CEDILLA
to U+0219 LATIN SMALL LETTER S WITH COMMA BELOW

Third:
from U+0162 LATIN CAPITAL LETTER T WITH CEDILLA
to U+021A LATIN CAPITAL LETTER T WITH COMMA BELOW

Fuorth:
from U+0163 LATIN SMALL LETTER T WITH CEDILLA
to U+021B LATIN SMALL LETTER T WITH COMMA BELOW

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

We have no mechanism to do this right now, and building one would take some care to avoid doing unwanted conversions.

You could work around this by exporting Romanian translations, running a search-and-replace, and re-uploading them if there have been changes.

Changed in rosetta:
status: New → Won't Fix
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Jeroen, what cases are there when Romanian uses U+015E and it should *not* be converted to U+0218, etc? If there aren't any, then unwanted conversions would not be an issue.

That we have no mechanism to do this seems like begging the question -- that's not a reason that the function shouldn't be implemented, it's why this bug was reported in the first place.

Revision history for this message
Данило Шеган (danilo) wrote :

I've discussed this with Adi (he emailed me directly), and I promised we'd look into it.

My original thoughts have been to prepare a message-filter script which would allow filtering by language and project, and running appropriate filter on it (it could be as simple as running sed, eg. exactly like msgfilter does for PO files).

However, implementing per-language, per-project rules in web interface is something that's going to be much harder, and would require much further discussion and thought.

Revision history for this message
Adi Roiban (adiroiban) wrote :

I had made this request after I found out that Fedora Romanian Transaltion team was using a webpage translation tool implementing this features.

The software is called Narro and is developed by the guy working at Romanian mozilla and open office translation http://code.google.com/p/narro/

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I understand why the filtering would need to be per-language, but I don't see that it would need to be per-project. Presumably Windows XP encourages the same errors regardless of what you're translating.

Changed in rosetta:
status: Won't Fix → New
Revision history for this message
Adi Roiban (adiroiban) wrote :

This is a per-language filter as comma below characters are standard in Romanian language in the last 3 years.

A project may decide not to use standards characters but rather go to support legacy characters. But I think this is rare case and new translations will be created for the current standards.

Changed in rosetta:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Alexandru Szasz (alexxed) wrote :

It's simpler to fix this at user leve. This problem would be easily solved by introducing a javascript snippet, can that be done for the Romanian locale only ?

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

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

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