[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Health-dev] Is the translation of reports buildin gnuhealth useful
From: |
Feng Shu |
Subject: |
Re: [Health-dev] Is the translation of reports buildin gnuhealth useful in practice? |
Date: |
Mon, 18 Jul 2022 16:37:20 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Luis Falcon <falcon@gnuhealth.org> writes:
> Dear Tumashui
> On Mon, 18 Jul 2022 09:30:39 +0800
> Feng Shu <tumashu@163.com> wrote:
>
>> Hello:
>>
>> This may be not a good question :-), when I translate gnuhealth to
>> zh_CN, I have found that many po items about reports have problem, I
>> would like to improve these reports files.
>>
>> But the first question is that the reports buildin gnuhealth are used
>> by user in other country? or buildin reports are just example? is it
>> worth to translate them? What about set reports to no translatable?
>
> Yes, they are used in the implementations worldwide. Of course, some of
> them are further customized to better fit their needs.
>
> In my experience, the majority (lab reports, evaluations, demographics,
> clinical history,...) use the GH default report.
OK, another questions is that:
Can we big change these buildin reports's style while stay the same fields?
for example: using more table column and row?
I don't know whether the aesthetics of different countries are
different. In my opinion, some reports are not very good-looking :-)
Maybe we should rely more on simple table? for example:
>
appointment_receipt.fodt
Description: Binary data
> Enjoy the week!
> Luis
--