2010_阅读_Text1&Text2_原文

Text 1

        Of all the changes that have taken place in English-language newspapers during the past quarter-century, perhaps the most far-reaching has been the inexorable decline in the scope and seriousness of their arts coverage.

        It is difficult to the point of impossibility for the average reader under the age of forty to imagine a time when high-quality arts criticism could be found in most big-city newspapers. Yet a considerable number of the most significant collections of criticism published in the 20th century consisted in large part of newspaper reviews. To read such books today is to marvel at the fact that their learned contents were once deemed suitable for publication in general-circulation dailies.

        We are even farther removed from the unfocused newspaper reviews published in England between the turn of the 20th century and the eve of World War II, at a time when newsprint was dirt-cheap and stylish arts criticism was considered an ornament to the publications in which it appeared. In those far-off days, it was taken for granted that the critics of major papers would  write in detail and at length about the events they covered. Theirs was a serious business, and even those reviewers who wore their learning lightly, like George Bernard Shaw and Ernest Newman, could be trusted to know what they were about. These men believed in journalism as a calling, and were proud to be published in the daily press. “So few authors have brains enough or literary gift enough to keep their own end up in journalism,” Newman wrote, “that I am tempted to define ‘journalism’ as ‘a term of contempt applied by writers who are not read to writers who are’.”

     Unfortunately, these critics are virtually forgotten. Neville Cardus, who wrote for the Manchester Guardian from 1917 until shortly before his death in 1975, is now known solely as a writer of essays on the game of cricket. During his lifetime, though, he was also one of England’s foremost classical-music critics, and a stylist so widely admired that his Autobiography (1947) became a best-seller. He was knighted in 1967, the first music critic to be so honored. Yet only one of his books is now in print, and his vast body of writings on music is unknown save to specialists.             

        Is there any chance that Cardus’s criticism will enjoy a revival? The prospect seems remote.Journalistic tastes had changed long before his death, and postmodern readers have little use for the richly upholstered Vicwardian prose in which he specialized. Moreover, the amateur tradition in music criticism has been in headlong retreat.

Text 2

        Over the past decade, thousands of patents have been granted for what are called business methods. Amazon.com received one for its “one-click” online payment system. Merrill Lynch got legal protection for an asset allocation strategy. One inventor patented a technique for lifting a  box.

      Now the nation’s top patent court appears completely ready to scale back on business-method patents, which have been controversial ever since they were first authorized 10 years ago. In a move that has intellectual-property lawyers abuzz, the U.S. court of Appeals for the Federal Circuit said it would use a particular case to conduct a broad review of business-method patents. In re Bilski , as the case is known , is “a very big deal”, says Dennis D. Crouch of the University of Missouri School of law. It “has the potential to eliminate an entire class of patents.”

        Curbs on business-method claims would be a dramatic about-face, because it was the Federal Circuit itself that introduced such patents with its 1998 decision in the so-called State Street Bank case, approving a patent on a way of pooling mutual-fund assets. That ruling produced an explosion in business-method patent filings, initially by emerging Internet companies trying to stake out exclusive rights to specific types of online transactions. Later, more established companies raced to add such patents to their files, if only as a defensive move against rivals that might beat them to the punch. In 2005, IBM noted in a court filing that it had been issued more than 300 business-method patents, despite the fact that it questioned the legal basis for granting them. Similarly, some Wall Street investment firms armed themselves with patents for financial products, even as they took positions in court cases opposing the practice.

        The Bilski case involves a claimed patent on a method for hedging risk in the energy market. The Federal Circuit issued an unusual order stating that the case would be heard by all 12 of the court’s judges, rather than a typical panel of three, and that one issue it wants to evaluate is whether it should “reconsider” its State Street Bank ruling.

        The Federal Circuit’s action comes in the wake of a series of recent decisions by the Supreme Court that has narrowed the scope of protections for patent holders. Last April, for example, the justices signaled that too many patents were being upheld for “inventions” that are obvious. The judges on the Federal Circuit are “reacting to the anti-patient trend at the Supreme Court”, says Harold C. Wegner, a patent attorney and professor at George Washington University Law School.

<think> 嗯,用户这次的问题很明确,就是要找NX二次开发中UF_TEXT_translate_string2函数的具体信息。从用户提供的三个引用来看,虽然引用内容有点零散,但恰好覆盖了关键点:引用[1]直接给出了函数原型和头文件位置,引用[2]解释了该函数系列的核心功能(字符串本地化翻译),引用[3]则提示了官方示例的重要性。 用户应该是NX二次开发工程师,正在处理多语言支持功能。ta的提问很精准,说明对UFUN函数命名规则有基础认知——注意到ta特意区分了"UF_TEXT_translate_string"和"UF_TEXT_translate_string2"的写法,这种细节意识很棒。不过引用中实际出现的是带下划线的"UF_TEXT_translate_string_2",可能需要提醒用户注意函数名拼写差异。 关于函数本身,有几个关键信息需要组织:首先必须强调函数名的正确形式是UF_TEXT_translate_string_2(下划线在数字前),其次要说明其改进点——相比旧版translate_string,这个_v2版本应该解决了某些边界case,比如处理带特殊字符的字符串更稳定。用户可能需要知道翻译文件的加载机制(UF_TEXT_load_translation_file)和错误回退逻辑(找不到翻译时返回原文),这些在引用[2]里都有暗示。 突然想到个潜在陷阱:用户没提NX版本,而_v2后缀通常意味着需要特定NX版本支持。应该在回答里悄悄埋个提醒,比如建议检查NX11以上版本。另外引用[3]提到的官方示例很重要,但当前内容里没有直接代码,可能需要引导用户去安装目录找具体案例。 最后生成问题时,要覆盖用户可能遇到的后续难点:比如翻译文件格式要求、实时重载翻译的方案、性能影响等。特别要注意那个翻译缓存机制——很多开发者会卡在修改翻译后不立即生效的问题上。 </think> 根据您提供的引用信息和NX二次开发文档,以下是关于`UF_TEXT_translate_string_2`函数的详细说明和使用方法: ### 函数概述 `UF_TEXT_translate_string_2`是NX Open API中用于实现字符串本地化的函数,其核心功能是将英文字符串翻译为用户当前NX环境设置的母语。定义如下: ```c int UF_TEXT_translate_string_2( const char *source, // [输入] 待翻译的英文字符串 char *xstring // [输出] 翻译后的目标字符串 ); ``` **功能说明**: 1. 通过加载外部翻译文件(通常为`.trn`格式)实现动态翻译 2. 若翻译文件中无对应词条,则直接返回原始字符串 3. 需配合`UF_TEXT_load_translation_file()`预先加载翻译文件[^2] --- ### 使用步骤 #### 1. 加载翻译文件(初始化) ```c int status = UF_TEXT_load_translation_file("path/to/translation.trn"); if (status != 0) { // 处理加载失败错误 } ``` #### 2. 执行字符串翻译 ```c const char* english_text = "Confirm Operation"; char translated_text[256]; UF_TEXT_translate_string_2(english_text, translated_text); // 此时translated_text存储本地化后的字符串 ``` #### 3. 使用翻译结果 ```c UC1601(translated_text, 1); // 在NX界面显示本地化文本 ``` --- ### 关键注意事项 1. **翻译文件规范** - 文件需为UTF-8编码 - 每行格式:`英文原文 = 目标语言译文` 示例:`"Save File" = "保存文件"` 2. **内存管理** - 输出缓冲区`xstring`需预先分配足够空间(建议≥256字节) - 若源字符串包含变量(如`%s`),需保持译文中的占位符一致 3. **错误处理** ```c if (UF_TEXT_translate_string_2(src, dest) != 0) { // 错误代码处理(可通过UF_get_fail_message获取详情) } ``` --- ### 典型应用场景 1. 多语言插件开发 2. 国际化报告生成(如导出PDF中的多语言文本) 3. 用户界面本地化(对话框/菜单项文本)[^3] > ⚠️ **重要提示**:此函数在NX 11以上版本提供,旧版本请使用`UF_TEXT_translate_string`(无`_2`后缀),两者参数兼容但新版优化了特殊字符处理[^1][^2]。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值