View Bug Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001366DCP-o-matici18npublic2018-09-11 13:232018-10-17 20:16
ReporterCarsten Assigned Tocarl  
PrioritylowSeveritytweakReproducibilityN/A
Status closedResolutionno change required 
PlatformMacOSOS X OS Version10.11
Product Version2.14.0 
Target Version2.14.0 
Summary0001366: No bug, but request for clarification - i18n between stable and test releases
Description

Hi Carl,

I just noticed that some of my german translations come out grossly wrong in 2.13.48 - basically, because sometimes I chose very explicit context related translations for otherwise generic terms (as for 'Timing'). When that generic term is then later used in a different app context, the original context reference in the translation goes havoc, of course.

But - these translations stay okay in the (backported) 2.12.10.

How do you keep track of those changes between stable and test versions, especially when backporting?
Would there be a need to have separate po files between stable and test versions? Does po-edit offer ways to keep track of these? I guess currently this is handled on the git level?

Now, what happens if I correct these issues for 2.13.48 in the current po file, when another stable release is later issued? Is it possible to freeze i18n for stable releases/backports.

  • Carsten
TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredUnknown

Activities

carl

2018-09-11 15:23

administrator   ~0002674

The files on dcpomatic.com/i18n are from 2.13.x. 2.12.x translations are effectively frozen at this point, so if you send changes to po files you don't have to worry as 2.12.x will not change.

Carsten

2018-09-11 15:43

manager   ~0002675

Okay, so, the only 'critical' part in this would be if something that is backported needs a new localization. Which probably doesn't happen often, as the backports/bug fixes usually do not introduce 'new' things, but only correct issues on the code level.

I keep all my previous localizations, so, if needed, I could easily reconnect to po files for e.g. 2.12.5 or so. Or at least those that I actually worked on.

  • Carsten

carl

2018-09-11 15:48

administrator   ~0002676

All the old .po files are in git and could be made downloadable on the website, but it shouldn't be necessary as strings very rarely change in 2.12.x. If any corrections are needed the files can be recovered from git.

Bug History

Date Modified Username Field Change
2018-09-11 13:23 Carsten New Bug
2018-09-11 13:23 Carsten Status new => assigned
2018-09-11 13:23 Carsten Assigned To => carl
2018-09-11 13:24 Carsten Description Updated
2018-09-11 13:27 Carsten Description Updated
2018-09-11 15:23 carl Note Added: 0002674
2018-09-11 15:43 Carsten Note Added: 0002675
2018-09-11 15:48 carl Note Added: 0002676
2018-10-17 10:37 carl Status assigned => resolved
2018-10-17 10:37 carl Resolution open => no change required
2018-10-17 20:16 carl Status resolved => closed