Sent via BlackBerry from T-Mobile
-----Original Message----- From: support-request@drupal.org Date: Wed, 25 Oct 2006 12:00:02 To:support@drupal.org Subject: support Digest, Vol 46, Issue 26
Send support mailing list submissions to support@drupal.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/listinfo/support or, via email, send a message with subject or body 'help' to support-request@drupal.org
You can reach the person managing the list at support-owner@drupal.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of support digest..."
Today's Topics:
1. Re: local.module and filtering strings (Kobus Myburgh)
----------------------------------------------------------------------
Message: 1 Date: Wed, 25 Oct 2006 08:03:29 +0200 From: "Kobus Myburgh" ITBJDM@puknet.puk.ac.za Subject: Re: [support] local.module and filtering strings To: support@drupal.org Message-ID: s53f1a61.037@pcm-nov-gwia-server.puk.ac.za Content-Type: text/plain; charset=US-ASCII
This is rather difficult to do. It might be possibly if you only use imported strings as the comments that the strings have (see the POT
I see your point.
I wonder if the solution we envision for the translations teams might
be
a solution for you: We plan to have a Drupal site where you can translate any Drupal strings inline, i.e. where they occur on the
Drupal
page. This will however rely on JavaScript and I don't know how well
screenreaders support this nowadays.
I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed.
Groete,
Kobus
------------------------------