Hello everyone, long time no talk!
I hope everyone has been well. I've had... a hectic time of it but I'm settling down finally.
I should apologize for how MIA and hard-to-reach I have been.
Hopefully now that things are more stable in my personal life, I can give more time to CL and other projects.
As a start, I've written a basic design update for Common-Lisp.net. You can view and comment on the code for it here: https://gitlab.common-lisp.net/clo/site/merge_requests/1
This features actual mobile responsiveness (yes, the last design had an embarrassing mistake, I know!) and removes the mtime dependency that was preventing us from upgrading Ruby on CLnet's servers. I think we're still on a very old Ruby version, hopefully this will allow us to upgrade it, or at least remove one more barrier.
Please take your time to review it at your leisure; I know I'm sort of surprising everyone with this.
I've attached a few screenshots so you can see what it looks like at a glance.
Thank you,
- C. Yang
Hi,
Sorry, yes, wrong list!
Thanks for the pointers! Ik use them while mailing the right list.
Regards,
Erik
On Mar 5, 2018 22:22, "Daniel Herring" <dherring(a)tentpost.com> wrote:
Hi Erik,
Did this get sent to the wrong list?
Anyway, I would recommend mimicking Qt's approach to translation. If
possible, re-use their file formats. Then you can use their toolchain for
maintaining translations.
http://doc.qt.io/qt-5/linguist-overview.html
- Daniel
On Mon, 5 Mar 2018, Erik Huelsmann wrote:
Hi,
>
> In our translation catelog, we have the word "To". There are multiple uses
> for this word, which is marked for translation for all uses.
>
> One use is the case of a date range ("From ... To ...."). Another use is
> the case of an address ("To: <address on the next line(s)>".
>
> When translating these to Dutch, these use cases have very different
> translations (Date range: "Tot"; address: "Aan").
>
> It seems we need some context specific translations. However, our
> translation library (which isn't gettext), doesn't cater for them.
>
> Any ideas as to how to approach this problem?
>
> How will we know which domains we need to distinguish?
>
>
>
> --
> Bye,
> Erik.
>
> http://efficito.com -- Hosted accounting and ERP.
> Robust and Flexible. No vendor lock-in.
>
>
Hi,
In our translation catelog, we have the word "To". There are multiple uses
for this word, which is marked for translation for all uses.
One use is the case of a date range ("From ... To ...."). Another use is
the case of an address ("To: <address on the next line(s)>".
When translating these to Dutch, these use cases have very different
translations (Date range: "Tot"; address: "Aan").
It seems we need some context specific translations. However, our
translation library (which isn't gettext), doesn't cater for them.
Any ideas as to how to approach this problem?
How will we know which domains we need to distinguish?
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.