Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#312 i18n revision due

GREEN
open
Martin Holmes
5
2014-10-03
2011-11-02
Sebastian Rahtz
No

In the last couple of years there have been a number of small revisions to wording of <desc> or <gloss>, and additions of new elements, which means that the translations are slightly out of sync. It is time to return to the translators and give them a (hopefully small..) list of things to check.

Related

Bugs: #312

Discussion

1 2 > >> (Page 1 of 2)
  • Lou Burnard
    Lou Burnard
    2012-03-18

    • milestone: 871213 --> 871214
     
  • Lou Burnard
    Lou Burnard
    2012-03-18

    I'm changing this to amber because it's not clear to me that we know how to ensure this gets done, nor even how to determine which bits need re-translating.

     
  • Martin Holmes
    Martin Holmes
    2012-03-18

    We can use svn log and grep to find any <desc> or <gloss> elements that have changed since the date of each translation in the file. That shouldn't be hard at all, surely?

     
  • There is a script at Utilities-1/CheckI18N.sh which was my attempt at this a few years ago. It needs a rethink, but the job is doable. For every gloss and desc, extract todays version and compare with the version as of the date in @version. Separately, find all the <desc> and <gloss> which have no translations at all (ie which are new).

    There's a good day's work here to refine the scripting, to get to the stage where one can offer a report to translators of what needs doing.

     
  • Martin Holmes
    Martin Holmes
    2012-03-19

    I'll take that on, if someone can tell me the start date (i.e. the last date when we know the translations were all up to date).

     
  • there never was a time when everything was up to date; but I dont think you need to know. I have in mind a simple:

    for each //gloss|desc
    extract just that element to fileA
    revert the containing file back to the date in @version
    extract just that element to fileB
    diff fileA fileB
    done

     
  • Martin Holmes
    Martin Holmes
    2012-03-19

    That makes sense. Which languages do we do this for? All of them? Different files seem to have different collections of languages.

     
  • James Cummings
    James Cummings
    2012-04-13

    I agree that this needs to be done in a consistent and scriptable way... specifically we should be able to output information of when different language versions were updated for any desc on the website. (It might be good to be able to display both when the english element was changed and when this particular language version was last updated on any particular output form.)

     
  • James Cummings
    James Cummings
    2012-04-16

    • milestone: 871214 --> GREEN
     
  • James Cummings
    James Cummings
    2012-04-18

    Council 2012 f2f in Ann Arbor decides: Rahtz to implement and kick off ongoing internationalisation updates. Also to check FM1 to see if translator's list is up to date.

     
  • Lou Burnard
    Lou Burnard
    2012-09-12

    Providing translations for the <desc>s of new elements should be given priority, it seems to me. Can we generate a list of those easily? Maybe we should try crowd-sourcing this problem?

     
    • assigned_to: rahtz --> martindholmes
     
  • Martin Holmes
    Martin Holmes
    2012-10-07

    This is a list of all elements which have no translations at all (meaning no <desc>s with @versionDate):

    calendar
    classRef
    constraint
    constraintSpec
    dim
    elementRef
    gb
    licence
    line
    listChange
    listForest
    listTranspose
    macroRef
    metamark
    mod
    notatedMusic
    pc
    precision
    redo
    retrace
    scriptDesc
    scriptNote
    sourceDoc
    spGrp
    styleDefDecl
    substJoin
    summary
    surfaceGrp
    transpose
    undo

     
  • Martin Holmes
    Martin Holmes
    2013-10-22

    A discussion on the Council list has brought this ticket alive again. We now have a plan to generate spreadsheets for Google, one for each language, with (per Sebastian):

    column 1: element/class name
    column 2: attribute name (where appropriate)
    column 3: <desc>
    column 4: translation (if any)
    column 5: <gloss>
    column 6: translation (if any)
    column 7: <remarks>
    column 8: translation (if any)
    column 9: reap statement (optional)

    and then ask would-be translators to edit the spreadsheets. From those, we selectively cull newly-supplied or edited translations and put them back into the specs.

     
  • Lou Burnard
    Lou Burnard
    2013-10-22

    This looks good, but

    (a) what on earth is a "reap statement"?

    (b) should we record whether or not the spec includes at least one example in the target language too?

     
  • Martin Holmes
    Martin Holmes
    2013-10-22

    I assume the "reap statement" is the indicator that says whether the translation is out of date (in other words, the English source has changed subsequent to the versionDate on the translation).

     
  • See script at P5/Utilities/catalogue-fori18n.xsl

     
  • On 22 Oct 2013, at 17:10, Lou Burnard louburnard@users.sf.net
    wrote:

    This looks good, but

    (a) what on earth is a "reap statement"?

    <resp>

    (b) should we record whether or not the spec includes at least one example in the target language too?

    i'd wonder if that was a rather different area of expertise

    Sebastian Rahtz
    Director (Research) of Academic IT
    University of Oxford IT Services
    13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

     
  • Lou Burnard
    Lou Burnard
    2013-10-22

    It doesn't take much expertise to see whether there is one or not.
    Supplying it if there isn't is a different question, of course.

    On 22/10/13 17:58, Sebastian Rahtz wrote:

    On 22 Oct 2013, at 17:10, Lou Burnard louburnard@users.sf.net
    louburnard@users.sf.net
    wrote:

    This looks good, but
    
    (a) what on earth is a "reap statement"?
    
    (b) should we record whether or not the spec includes at least one
    example in the target language too?
    
    i'd wonder if that was a rather different area of expertise
    

    Sebastian Rahtz
    Director (Research) of Academic IT
    University of Oxford IT Services
    13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431


    [bugs:#312] http://sourceforge.net/p/tei/bugs/312/ i18n revision due

    Status: open
    Labels: Internationalization
    Created: Wed Nov 02, 2011 10:46 AM UTC by Sebastian Rahtz
    Last Updated: Tue Oct 22, 2013 04:55 PM UTC
    Owner: Martin Holmes

    In the last couple of years there have been a number of small
    revisions to wording of or <gloss>, and additions of new
    elements, which means that the translations are slightly out of sync.
    It is time to return to the translators and give them a (hopefully
    small..) list of things to check.


    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/tei/bugs/312/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Bugs: #312

  • it doesn't take any expertise at all to see whether there is an example for language X, we can do that as part of the transformation to the table....

     
  • James Cummings
    James Cummings
    2013-11-09

    Might it be possible to have a form that uses this as a data source and so presents a rendered view of this and allows them to update a textbox with the translation?

     
  • in what way is the Google spreadsheet not providing exactly that functionality?

     
  • Martin Holmes
    Martin Holmes
    2013-12-20

    Emailed original French team leader 2013-11-18; no response. Wrote to AC and FC re Italian 2013-12-20. Wrote to MB re Chinese 2013-12-20.

     
    Last edit: Martin Holmes 2013-12-20
1 2 > >> (Page 1 of 2)