OASIS XML Localisation Interchange File Format (XLIFF) TC

 View Only
  • 1.  Leaving the XLIFF TC

    Posted 10-24-2016 20:53
    Hi All,   I wanted to let you know that, unfortunately, I’ll be leaving the XLIFF Technical Committee, effective immediately.   I will be leaving Microsoft in the next week and relocating with my family back to Dublin. My next career move will take me outside the world of localization, as I will be working on document productivity opportunities with Nitro.   I’ve been sharing progress of the XLIFF TC with my colleagues here internally and they will consider who may be best to represent Microsoft in the TC.   Although I haven’t had much time to dedicate to the TC in recent times, I genuinely enjoyed working with all of you during the XLIFF 2.0 days and meeting up at the various XLIFF symposia. I’m very pleased at the progress that the XLIFF TC made and how far the standard has evolved in recent years, including becoming the mainstream file format for localization within Microsoft. I’ll continue to be a champion for XLIFF whenever the opportunity allows J .   I wish you all the best for the future and hope our paths cross again. I can be reached at my personal email address – kevinod@gmail.com – or on LinkedIn .   Best regards, Kevin.


  • 2.  Re: [xliff] Leaving the XLIFF TC

    Posted 10-25-2016 05:48



    Kevin


    Really sorry to see you leave the TC but I'm sure you're excited to be moving home.


    Thanks for the awesome work you and Ryan put into open sourcing the XLIFF library.


    Congratulations for the new job and best wishes for you and your family back in Dublin.


    Phil





    On 24 Oct 2016, at 14:14, Kevin O'Donnell < kevinod@microsoft.com > wrote:







    Hi All,
     
    I wanted to let you know that, unfortunately, I’ll be leaving the XLIFF Technical Committee, effective immediately.

     
    I will be leaving Microsoft in the next week and relocating with my family back to Dublin. My next career move will take me outside the world of localization, as I will be working on document productivity opportunities with Nitro.
     
    I’ve been sharing progress of the XLIFF TC with my colleagues here internally and they will consider who may be best to represent Microsoft in the TC.
     
    Although I haven’t had much time to dedicate to the TC in recent times, I genuinely enjoyed working with all of you during the XLIFF 2.0 days and meeting up at the various XLIFF symposia. I’m very pleased at the progress that the XLIFF
    TC made and how far the standard has evolved in recent years, including becoming the mainstream file format for localization within Microsoft. I’ll continue to be a champion for XLIFF whenever the opportunity allows
    J .
     
    I wish you all the best for the future and hope our paths cross again. I can be reached at my personal email address –
    kevinod@gmail.com – or on
    LinkedIn .
     
    Best regards,
    Kevin.







    Phil   Ritchie
    Chief Technology Officer Vistatec
    Vistatec House, 700 South Circular Road,
    Kilmainham, Dublin 8, Ireland.
    Tel: +353 1 416 8000
    Direct:
    +353 1 416 8024
    Email:
    phil.ritchie@vistatec.com
    www.vistatec.com  
    ISO 9001 ISO 13485 EN 15038





    Think Global


         





    Vistatec Ltd. Registered in Ireland 268483.
    Registered Office, Vistatec House, 700, South Circular Road, Kilmainham. Dublin 8. Ireland.
    The information contained in this message, including any accompanying documents, is confidential and is intended only for the addressee(s). The unauthorized use, disclosure, copying, or alteration of this message is strictly forbidden. If you have received
    this message in error please notify the sender immediately.










  • 3.  RE: Leaving the XLIFF TC

    Posted 10-25-2016 16:10
    Hi Kevin,   Thank you for all the great contributions you’ve made to the TC and to the mainstreaming of XLIFF. I think there were a few key events that happened over the years to help move XLIFF into a more ubiquitous standard in the L10N community. In my mind no doubt one of the biggest was Microsoft joining the TC and the fresh energy you, Ryan, and Uwe brought.   Best wishes going forward. I too hope our paths cross in the future.   Thanks,   Bryan Schnabel Sr. Manager, Web Experience Team T / +1 503.627.5282 M / +1 503.327.4778 tek.com   From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Kevin O'Donnell Sent: Monday, October 24, 2016 1:52 PM To: XLIFF Main List Subject: [xliff] Leaving the XLIFF TC   Hi All,   I wanted to let you know that, unfortunately, I’ll be leaving the XLIFF Technical Committee, effective immediately.   I will be leaving Microsoft in the next week and relocating with my family back to Dublin. My next career move will take me outside the world of localization, as I will be working on document productivity opportunities with Nitro.   I’ve been sharing progress of the XLIFF TC with my colleagues here internally and they will consider who may be best to represent Microsoft in the TC.   Although I haven’t had much time to dedicate to the TC in recent times, I genuinely enjoyed working with all of you during the XLIFF 2.0 days and meeting up at the various XLIFF symposia. I’m very pleased at the progress that the XLIFF TC made and how far the standard has evolved in recent years, including becoming the mainstream file format for localization within Microsoft. I’ll continue to be a champion for XLIFF whenever the opportunity allows J .   I wish you all the best for the future and hope our paths cross again. I can be reached at my personal email address – kevinod@gmail.com – or on LinkedIn .   Best regards, Kevin. Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.