Re: [nvda-translations] OCR translation
- From: Takuya Nishimoto <nishimotz@xxxxxxxxx>
- To: nvda-translations@xxxxxxxxxxxxx
- Date: Fri, 8 Feb 2013 14:24:05 +0900
Thank you.
Just a thought, is it possible to build add-on web page using the
manifest of the add-on itself?
I agree that web pages may contain additional information for some add-ons,
but basically descriptions would be same if the manifests are well-written.
Best regards,
--
Takuya Nishimoto
On Fri, Feb 8, 2013 at 5:36 AM, James Teh <jamie@xxxxxxxxxxxx> wrote:
> On 7/02/2013 11:24 PM, Takuya Nishimoto wrote:
>>
>> I would like to translate OCR add-on into Japanese.
>> What is the conclusion of ticket 2744?
>> Possibility of translating OcR addon
>
> I need to get around to writing an SConstruct for the OCR add-on. It is
> somewhat more complicated than the basic template, so it's not just a matter
> of using that.
>
>
>> I understand that the use of single PO file for multiple purposes is
>> not efficient,
>> but reducing the work of translators and avoiding system errors are
>> important, in my opinion.
>
> Sure, but if we're going to do this, it'd probably make sense to get rid of
> the locale specific manifest files as I outlined here:
> http://www.nvda-project.org/ticket/2819
>
>
>> How about using single PO file for localizing the add-on web page, as
>> well as add-on itself and the manifest file?
>
> Imo, this isn't feasible. It doesn't make sense for the add-on to include
> stuff for the web page, especially since there could be large bodies of text
> and all of this is loaded into memory.
>
> Thanks,
> Jamie
>
> --
> James Teh
> Director, NV Access Limited
> Email: jamie@xxxxxxxxxxxx
> Web site: http://www.nvaccess.org/
> Phone: +61 7 5667 8372
>
Other related posts:
