blocks|key|1831954|text|来自模糊项的gettext|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1831955|模糊条目，即使它们解释了大多数其他目的的翻译条目，通常需要译者进行修改。这些可能是通过应用程序msgmerge来根据新的PO模板文件更新旧的已翻译的PO文件来产生的，当这个工具假设一些新的msgid只被稍微修改了一些旧的msgid，并选择对它认为是新修改的条目的旧翻译。原始字符串(+msgid字符串)的轻微更改通常应该反映在已翻译的字符串中，这需要译者的干预。因此，msgmerge可能会将一些条目标记为模糊的。|blockquote|1831956|我看到了#,+fuzzy在使用Django生成消息文件(.po)时出现，以及原始文本(msgid)被更改的地方，在这种情况下，译者应该知道翻译文本也应该更改。|style|CODE|1831957|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/gettext/manual/html_node/gettext_9.html#Fuzzy-Entries^0|2|B|0|0|0|4|8|17|5|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|X|8|@$A|Y|B|Z|I|J]|$A|10|B|11|I|J]]|9|@]|C|$]]|$1|K|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

From <a href="http://www.gnu.org/software/gettext/manual/html_node/gettext_9.html#Fuzzy-Entries" rel="nofollow">gettext on Fuzzy-Entries</a>:

<blockquote>
 Fuzzy entries, even if they account for translated entries for most other purposes, usually call for revision by the translator. Those may be produced by applying the program msgmerge to update an older translated PO files according to a new PO template file, when this tool hypothesises that some new msgid has been modified only slightly out of an older one, and chooses to pair what it thinks to be the old translation for the new modified entry. The slight alteration in the original string (the msgid string) should often be reflected in the translated string, and this requires the intervention of the translator. For this reason, msgmerge might mark some entries as being fuzzy. 
</blockquote>

I have seen <code>#, fuzzy</code> appear in when generating a message file (.po) using Django, and where the original text (<code>msgid</code>) was changed, in which case the translator should be aware that the translated text should be changed as well.

blocks|key|2621268|text|当xgettext在消息文件中自动生成项目标题时，它会在顶部添加#,+fuzzy条目。这句话本身并没有什么特别的意义:它只是指出一个人需要来填补空白。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2621269|让我们更深入地挖掘源代码。|2621270|当您第一次创建消息文件时，xgettext将项目信息添加到生成的消息文件的顶部(除非您传递--omit-header)：|2621271|$+cat+hello.c
int+main()+{
++printf(gettext("Hello+World\n"));
++return+0;
}

$+xgettext+-o-+hello.c
#+SOME+DESCRIPTIVE+TITLE.
#+Copyright+(C)+YEAR+THE+PACKAGE'S+COPYRIGHT+HOLDER
#+This+file+is+distributed+under+the+same+license+as+the+PACKAGE+package.
#+FIRST+AUTHOR+<EMAIL@ADDRESS>,+YEAR.
#
#,+fuzzy
msgid+""
msgstr+""
"Project-Id-Version:+PACKAGE+VERSION\n"
"Report-Msgid-Bugs-To:+\n"
"POT-Creation-Date:+2017-06-08+11:51-0400\n"
"PO-Revision-Date:+YEAR-MO-DA+HO:MI%2BZONE\n"
"Last-Translator:+FULL+NAME+<EMAIL@ADDRESS>\n"
"Language-Team:+LANGUAGE+<LL@li.org>\n"
"Language:+\n"
"MIME-Version:+1.0\n"
"Content-Type:+text/plain;+charset=CHARSET\n"
"Content-Transfer-Encoding:+8bit\n"

#:+hello.c:3
#,+c-format
msgid+"Hello+World\n"
msgstr+""|code-block|syntax|javascript|2621272|支持这一点的逻辑可以在xgettext.c:construct_header()中找到。在该函数的底部，新生成的标头信息被标记为模糊：|2621273|mp->is_fuzzy+=+true;|2621274|由于此文本已被标记为模糊，因此将#,+fuzzy注释标记添加到文本中。这里的目的是提高人们的认识:计算机程序将文本添加到消息文件中，而人类需要采取行动。特别是，一个人需要来填补空白:修订日期，译者姓名，语言，等等。|2621275|使用"#，fuzzy“注释在此上下文中是有意义的，如文档所示：|2621276|模糊条目通常需要译者进行修改。|blockquote|2621277|entityMap|0|LINK|mutability|MUTABLE|url|http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext-tools/src/xgettext.c#n3711^0|1|8|W|8|0|0|D|8|19|D|0|0|B|T|B|T|0|0|0|G|8|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1C|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1I|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@$9|1M|A|1N|1|1O]]|E|$]]|$1|Q|3|R|5|L|7|1P|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1T|8|@]|D|@]|E|$]]|$1|W|3|X|5|Y|7|1U|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|10|$11|$5|12|13|14|E|$15|16]]]]

<code>xgettext</code> adds the <code>#, fuzzy</code> entry at the top when it auto-generates a project header in the message file. The comment has no special meaning, per se: it's just noting that a human needs to come along and fill in the gaps.

Let's dig a little deeper into the source.

When you first create a message file, <code>xgettext</code> adds project information to the top of the generated message file (unless you pass <code>--omit-header</code>):

<pre><code>$ cat hello.c
int main() {
 printf(gettext("Hello World\n"));
 return 0;
}

$ xgettext -o- hello.c
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR &lt;EMAIL@ADDRESS&gt;, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-08 11:51-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME &lt;EMAIL@ADDRESS&gt;\n"
"Language-Team: LANGUAGE &lt;LL@li.org&gt;\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#: hello.c:3
#, c-format
msgid "Hello World\n"
msgstr ""
</code></pre>

The logic backing this is found in <a href="http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext-tools/src/xgettext.c#n3711" rel="noreferrer"><code>xgettext.c:construct_header()</code></a>. Way down at the bottom of that function, the newly-generated header information is marked fuzzy:

<pre><code>mp-&gt;is_fuzzy = true;
</code></pre>

Since this text has been marked as fuzzy, the <code>#, fuzzy</code> comment tag is added to the text. The intent here is to raise awareness: a computer program added text to the message file, and a human needs to take action. In particular, a human needs to come along and fill in the blanks: revision date, translator name, language, and so on.

Using the "#, fuzzy" annotation makes sense in this context, as per the docs:

<blockquote>
 [Fuzzy entries] usually call for revision by the translator.
</blockquote>

When using <code>xgettext</code> to generate a <code>.pot</code> file, at the top of the generated file I get this:

<pre><code># SOME DESCRIPTIVE TITLE.
...
#, fuzzy
...
</code></pre>

What does the <code>#, fuzzy</code> mean?

I know what it means if a translation is fuzzy (it is poor quality), but what does it mean at the top of a <code>.pot</code> file?

What does #, fuzzy mean at the top of a xgettext-generated .pot file?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当使用xgettext生成.pot文件时，在生成的文件顶部我得到如下信息：# SOME DESCRIPTIVE TITLE....#, fuzzy...#, fuzzy是什么意思？如果翻译是模糊的(质量很差)，我知道这意味着什么，但是在顶级中.pot文件意味着什么呢？

问在xgettext生成的.pot文件顶部#，模糊意味着什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在xgettext生成的.pot文件顶部#，模糊意味着什么？EN