WordPress.org

GlotPress

Opened 3 years ago

Last modified 20 months ago

#432 new enhancement

copy from informal/formal

Reported by: zodiac1978 Owned by:
Milestone: Future Release Priority: normal
Version: Component: General
Keywords: needs-patch Cc:

Description

At first: I know that just a few languages have a need for this. Maybe this can be activated locale specific.

Beside the "Copy from original" link, it would be great to have a "copy from informal/formal" so that we can copy the translation (if it exist!) from the other (formal or informal) project.

This would make it much easier to be consistent with each other and it would be much faster.

Change History (12)

#1 @bjornjohansen
3 years ago

A “Copy from <other>” where <other> can be defined per locale would be nice. Think of German, Spanish etc, where a lot of the regional locales could benefit from this.

#2 @thee17
3 years ago

Yes this feature would be excellent to have.

#3 @alvarogois
2 years ago

I'm not sure if this should be a comment or a new ticket, though it's related to this flow, so… my idea is this: some variants are very close to the default language, only some of the strings actually differ, at least in Portuguese (Portugal). I’m thinking of the formal vs. informal but also the orthographic differences like (our own pre and post Orthographic Reform). There should be a way, in GlotPress, to link variants to the default translation. This would allow to have only one translation flow, and changes to be simultaneous in all variants.

Now we have different flows, which makes it inefficient. My idea was, if possible, to actually have a “side-by-side” approach.

Since the way WordPress manages locales and language files seems to be changing fast, who knows if we can take the opportunity to go even further.

This ticket was mentioned in Slack in #polyglots by alvarogois. View the logs.


2 years ago

This ticket was mentioned in Slack in #polyglots by alvarogois. View the logs.


2 years ago

This ticket was mentioned in Slack in #polyglots by alvarogois. View the logs.


2 years ago

#7 @markoheijnen
2 years ago

  • Milestone changed from Awaiting Review to Future Release

Move this ticket to future release as this are tickets we want to implement.

This ticket was mentioned in Slack in #polyglots by alvarogois. View the logs.


2 years ago

This ticket was mentioned in Slack in #meta-i18n by ocean90. View the logs.


22 months ago

#10 @ivanrf
22 months ago

If a person speaks two languages (other than English), it will be easier to show one of them and let him translate to the other one. The only question would be if the essence or the meaning of the English text could be lost when doing this.

Similar to this ticket, it could be added a "Copy from <select>" below the "Copy from original" link, in order to choose one of the available locales for the project.

Then, you will see the "original" English text, but you can translate over the other locale.

This ticket was mentioned in Slack in #glotpress by alvarogois. View the logs.


21 months ago

This ticket was mentioned in Slack in #polyglots by alvarogois. View the logs.


20 months ago

Note: See TracTickets for help on using tickets.