Translation indicator-datetime appear strange contents



  • Hey, everybody.
    I recently showed this when I was translating indicator-datetime.2019-05-01 (1).png

    I can't translate at the moment.

    Source string commentary
    Chinese translations for PACKAGE package.
    Copyright (C) 2010 THE PACKAGE'S COPYRIGHT HOLDER
    This file is distributed under the same license as the PACKAGE package.
    Canonical OEM, 2010.

    Original Text

    "
    msgstr ""
    "Project-Id-Version: indicator-datetime
    "
    "Report-Msgid-Bugs-To: 
    "
    "POT-Creation-Date: 2010-03-10 15:20-0500
    "
    "PO-Revision-Date: 2010-03-03 10:06-0500
    "
    "Last-Translator: Canonical OEM
    "
    "Language-Team: Chinese (traditional)
    "
    "MIME-Version: 1.0
    "
    "Content-Type: text/plain; charset=UTF-8
    "
    "Content-Transfer-Encoding: 8bit
    "
    
    #: ../src/indicator-datetime.c:177
    msgid "Error getting time"
    msgstr "獲得時間發生錯誤"
    
    #. TRANSLATORS: This string is used for measuring the size of
    #. the font used for showing the time and is not shown to the
    #. user anywhere.
    #: ../src/indicator-datetime.c:259
    #, c-format
    msgid "%d%d:%d%d AM"
    msgstr "%d%d:%d%d 上午"
    
    #. TRANSLATORS: This string is used for measuring the size of
    #. the font used for showing the time and is not shown to the
    #. user anywhere.
    #: ../src/indicator-datetime.c:266
    #, c-format
    msgid "%d%d:%d%d PM"
    msgstr "%d%d:%d%d 下午"
    
    #: ../src/indicator-datetime.c:351
    msgid "Open Calendar"
    msgstr "開啟行事曆"
    
    #: ../src/indicator-datetime.c:361
    msgid "Set Time and Date..."
    msgstr "設定時間和日期...
    


  • @Louies what's the issue you're facing exactly? Is it fixed now?

    Edit: Ah! I understand the issue now 🙂 Every package has to have a license but that part is broken in indicator-datetime and it doesn't have a clean string to translate.

    @Flohack can you take a look at it? Thank you


  • Infrastructure

    Sure I will. This looks really bad!



  • @Flohack thank you!



  • @Flohack thanks


Log in to reply