discourse/plugins/discourse-solved/config/locales/client.zh_CN.yml

# WARNING: Never edit this file.
# It will be overwritten when translations are pulled from Crowdin.
#
# To work with us on translations, join this project:
# https://translate.discourse.org/

zh_CN:
  admin_js:
    admin:
      site_settings:
        categories:
          discourse_solved: "Discourse Solved"
      dashboard:
        highlights:
          kpi:
            accepted_solutions:
              label: "已被接受的解决方案"
              tooltip: "被标记为解决方案的帖子所构成的主题数量。"
        sections:
          support:
            title: "支持"
            fetch_error: "无法加载支持数据。"
            filter:
              all_categories: "所有类别"
            headline:
              healthy:
                title: "社区正在自行解决问题。"
              struggling:
                title: "大多数问题都没有得到解答。"
              mixed:
                title: "支持情况好坏参半。"
              no_data:
                title: "没有足够的支持活动"
                summary: "在该时间段内尚无支持活动。一旦有话题出现，您将看到您的社区是如何处理这些话题的。"
              resolution:
                up: "问题解决率提升至 %{rate} %。"
                down: "问题解决率降低至 %{rate} %。"
                flat: "问题解决率保持在 %{rate} %。"
              answerers:
                members: "用户回复了 %{share} %的回复。"
                staff: "管理人员回复了 %{share} %的回复。"
              reply:
                faster: "首次回复时间缩短至 %{time} ，比上一周期快了 %{delta} 。"
                slower: "首次回复时间延长至 %{time} ，比上一周期慢了 %{delta} 。"
                flat: "首次回复时间保持在 %{time} 。"
              unanswered:
                other: "此期间的%{count} 个话题仍无回复。"
            kpi:
              resolution_rate:
                label: "解决率"
                tooltip: "已解决支持话题的百分比。"
              staff_involvement:
                label: "管理人员参与"
                tooltip: "在所有未解决的支持话题中，由管理人员首次回复的百分比。"
              avg_first_reply:
                label: "平均首次回复时间"
                tooltip: "从支持话题发布，到收到第一个回复之间的平均时间。"
            outcomes:
              title: "话题类别"
              resolved:
                label: "已解决"
                tooltip: "标记为已解决的话题数量。"
              in_progress:
                label: "进行中"
                tooltip: "至少有一条回复的话题数量。"
              unanswered:
                label: "未解答"
                tooltip: "没有回复的话题数量。"
            answerers:
              title: "谁在回答？"
              empty: "在此期间没有任何回复。"
              staff: "管理人员"
              leader: "领导者"
              regular: "活跃用户"
              member: "成员"
              basic: "基本用户"
            response_time:
              title: "回复时间分布"
              buckets:
                lt_1h: "< 1 小时"
                "1_4h": "1–4 小时"
                "4_24h": "4–24小时"
                gt_24h: "> 24 小时"
              trend:
                faster: "%{duration} 更快"
                slower: "%{duration} 更慢"
                tooltip: "平均回复时间趋势。"
  js:
    notifications:
      alt:
        solved:
          accepted_notification: "已被接受"
          topic_solved_notification: "已解决"
    solutions: "解决方案"
    solved:
      title: "已解决"
      notify_on_solved: "当我正在跟踪或关注的话题被解决时通知我。仅适用于允许提供解答的类别话题。"
      allow_accepted_answers: "允许话题所有者和管理人员将回复标记为解决方案"
      solved_topics_auto_close_hours: "当话题被标记为已解决后，在最后回复 (n) 小时后自动关闭话题。"
      notify_on_staff_accept_solved: "当管理人员标记解决方案时通知话题创建者"
      empty_box_on_unsolved: "在话题列表中显示未解决的话题状态"
      accept_answer: "如果此回复解决了问题，请选择"
      accepted_description: "这是此话题被接受的解决方案"
      has_no_accepted_answer: "此话题尚无解决方案"
      unaccept_answer: "如果此回复不再解决问题，请取消选择"
      accepted_answer: "解决方案"
      solution: "解决方案"
      solution_summary:
        other: "解决方案"
      accepted_answer_solver_info: "由 %{user} 在 %{post} 中解决"
      accepted_answer_post_number: "帖子 %{post_number}"
      accepted_notification: "<p><span>%{username}</span> %{description}</p>"
      topic_status_filter:
        all: "所有"
        solved: "已解决"
        unsolved: "未解决"
      no_solved_topics_title: "您尚未解决任何话题"
      no_solved_topics_title_others: "%{username} 还没有解决任何话题"
      no_solved_topics_body: "当您对某个话题提供有用的回复时，您的回复可能会被话题所有者或管理人员选为解决方案。"
      marked_solved_by: "已被 %{user} 接受"
      confirm_move_solution_title: "移动解决方案帖子"
      confirm_move_solution:
        other: "您选择的其中一个帖子被标记为此话题的解决方案。如果您将其移动，话题将更新为未解决。"
      move_post_confirm:
        other: "移动帖子"
      move_post_cancel: "取消"
      dont_show_again: "知道了，不再显示"
      confirm_solved_removal_title: "解决方案将被移除"
      confirm_solved_removal: "此更改将禁用此话题的解决方案，并移除已接受的解决方案。"
      confirm_solved_removal_confirm: "确认"
      confirm_solved_removal_cancel: "取消"
      shared_issue:
        label: "我也是"
        label_with_count: "%{label} (%{count})"
        title: "我也遇到了这个问题。"
        author_title: "你发起了这个话题。"
        closed_title: "该话题已关闭"
        archived_title: "该话题已归档"
      no_answer:
        title: 您的问题是否已被解答？
        description: "在正确回复下方使用解决方案按钮高亮显示回答并帮助他人。"
      topic_solved_notification: "<p><span>%{username}</span> %{description}</p>"
      notification:
        title: "您的帖子已被标记为解决方案"
        topic_solved_title: "话题已解决"
      topic_notifications:
        tracking:
          description: "当有人通过 @ 名称提及您、回复您或话题被解决时，系统会通知您。将显示此话题的新回复数量。"
        watching:
          description: "您将在此话题获得新回复和话题得到解决时收到通知。系统会显示此话题的新回复数量。"
      category_type_support:
        title: "支持"
    topic_statuses:
      solved:
        help: "此话题有解决方案"
    search:
      advanced:
        statuses:
          solved: "已被解决"
          unsolved: "尚未解决"
    admin:
      web_hooks:
        solved_event:
          group_name: "已解决的事件"
          accepted_solution: "当用户将帖子标记为被接受的回答时"
          unaccepted_solution: "当用户将帖子标记为遭拒的回答时"
      api:
        scopes:
          descriptions:
            solved:
              answer: 接受/不接受解决方案。
    discourse_automation:
      triggerables:
        first_accepted_solution:
          max_trust_level:
            tl1: 信任级别 < 1
            tl2: 信任级别 < 2
            tl3: 信任级别 < 3
            tl4: 信任级别 < 4
            any: 任何
          fields:
            maximum_trust_level:
              label: 信任级别
              description: 此信任级别下的用户将触发此自动化