Re: [translate-pootle] Reset a user's password?

2008-07-14 Thread F Wolff
On Di, 2008-07-15 at 06:49 +0200, Charl van Niekerk wrote:
> On Fri, Jul 11, 2008 at 4:18 PM, Samuel Murray (Groenkloof)
> <[EMAIL PROTECTED]> wrote:
> > I agree completely, but let's face it, password reminders will not be
> > implemented anytime soon.  It is easier to simply make a change to one
> > of the HTML pages in the mean time.
> 
> Think again. :)
> 
> On Fri, Jul 11, 2008 at 5:01 PM, F Wolff <[EMAIL PROTECTED]> wrote:
> > It is really not that hard. But somebody has to actually try. Anybody
> > that knows a bit of programming is welcome to ask some questions on
> > #pootle or here.
> 
> I can do it if nobody else yet volunteered...
> 
> Do you need it before the end of the week or can I sort this over the weekend?
> 
> Cheers,
> Charl
> 

Great news, Charl!  There is no rush. I can give you some pointers over
IRC if you are interested.

Thanks again.
Friedel


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Reset a user's password?

2008-07-14 Thread Charl van Niekerk
On Fri, Jul 11, 2008 at 4:18 PM, Samuel Murray (Groenkloof)
<[EMAIL PROTECTED]> wrote:
> I agree completely, but let's face it, password reminders will not be
> implemented anytime soon.  It is easier to simply make a change to one
> of the HTML pages in the mean time.

Think again. :)

On Fri, Jul 11, 2008 at 5:01 PM, F Wolff <[EMAIL PROTECTED]> wrote:
> It is really not that hard. But somebody has to actually try. Anybody
> that knows a bit of programming is welcome to ask some questions on
> #pootle or here.

I can do it if nobody else yet volunteered...

Do you need it before the end of the week or can I sort this over the weekend?

Cheers,
Charl

-- 
Charl van Niekerk
http://charlvn.za.net

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


[translate-pootle] RFE: use "--author" when committing to a GIT repository

2008-07-14 Thread Christian Perrier
This comes from a discussion I just had with the maitnainers of dpkg
(the Debian package management utility), which we're about to add on
Debian'sPootle.

They want to give proper credit in their changelog file, to authors of
translations.

Tehrefore, they suggested using the "--author" switch of "git commit"
and put the translator's name there.

Would it be possible to use this, additionnally to what's already put
in the commit message?

It could even be possible to use the real name of the translator, and
not only his|her nickname on the Pootle server.



-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Patch for adding the ability to configure a project l10n directory from pootle admin page

2008-07-14 Thread Christian Perrier
Quoting Suresh Chandrasekharan ([EMAIL PROTECTED]):


> Not sure this is an issue...


Well, the point could also be that anything involving setting symlinks
to "random" stuff on the system ould be seen as a potential symlink
attack. So, in any case, that code has to be as carefully thought as
possible, certainly.



-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Patch for adding the ability to configure a project l10n directory from pootle admin page

2008-07-14 Thread Suresh Chandrasekharan

Miklos Vajna wrote:
> On Mon, Jul 14, 2008 at 08:40:28PM +0200, Christian Perrier <[EMAIL 
> PROTECTED]> wrote:
>   
>> When running Pootle as a non privileged user, these "secret" files
>> will remain protected (unless of course they're world-readable).
>> 
>   
Only admin can change the project settings, and so every user
cannot do this.

Moeover the system will only index and display .po and
.xlf files, so even if user is providing a link to /etc, nothing will
be displayed if that directory don't have any .po/.xlf files
> I think it's a bug if a user can read every file the pootle user can.
> Think of /etc/passwd and such files.
>
> While the fact that the pootle user can read it is not a problem, if an
> anonymous user can, that's heavily problematic IMHO.
>   
> 
>
> -
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>   
> 
>
> ___
> Translate-pootle mailing list
> Translate-pootle@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/translate-pootle
>   


-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Patch for adding the ability to configure a project l10n directory from pootle admin page

2008-07-14 Thread Miklos Vajna
On Mon, Jul 14, 2008 at 08:40:28PM +0200, Christian Perrier <[EMAIL PROTECTED]> 
wrote:
> When running Pootle as a non privileged user, these "secret" files
> will remain protected (unless of course they're world-readable).

I think it's a bug if a user can read every file the pootle user can.
Think of /etc/passwd and such files.

While the fact that the pootle user can read it is not a problem, if an
anonymous user can, that's heavily problematic IMHO.


pgptxZvGvAPU5.pgp
Description: PGP signature
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Patch for adding the ability to configure a project l10n directory from pootle admin page

2008-07-14 Thread Suresh Chandrasekharan
Christian Perrier wrote:
> Quoting Suresh Chandrasekharan ([EMAIL PROTECTED]):
>
>   
>> One concern that I heard in the #pootle channel is that the ability to 
>> do this will compromise
>> system security (in case the Pootle system is shared by different admins 
>> who are hostile
>> to each other) by somebody who will try out different path combinations 
>> and get the
>> access to secret po files which he is not authorized to read... Would 
>> like to get feedback
>> regarding this.
>> 
>
> Isn't this a concern only when people are running Pootle as root?
>
> When running Pootle as a non privileged user, these "secret" files
> will remain protected (unless of course they're world-readable).
>
>
>   
Sure, I thought people were concerned with the fact that this will allow 
admins
to wildly explore and will expose .po files in directories which are 
world readable
but they don't have any other way of accessing. Just think of this as 
someone
randomly trying some paths and hitting upon some thing which they should not
see.

You're right that this won't hurt a system with proper permissions, but 
will
further weaken ones which are already compromised.

Not sure this is an issue...
> -
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> ___
> Translate-pootle mailing list
> Translate-pootle@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/translate-pootle
>   


-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Patch for adding the ability to configure a project l10n directory from pootle admin page

2008-07-14 Thread Christian Perrier
Quoting Suresh Chandrasekharan ([EMAIL PROTECTED]):

> One concern that I heard in the #pootle channel is that the ability to 
> do this will compromise
> system security (in case the Pootle system is shared by different admins 
> who are hostile
> to each other) by somebody who will try out different path combinations 
> and get the
> access to secret po files which he is not authorized to read... Would 
> like to get feedback
> regarding this.


Isn't this a concern only when people are running Pootle as root?

When running Pootle as a non privileged user, these "secret" files
will remain protected (unless of course they're world-readable).



-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Search enhancements

2008-07-14 Thread Samuel Murray (Groenkloof)

Julen wrote:

> - listing all the search results in a single page

Yes, but even better would be the ability to actually edit segments on 
such a single page.  The problem with this would be... what to do when 
the user selects "submit".

Well, one hack would be this:  Open the "all results on one page" search 
page in a new window.  Instead of a "submit" button, have two buttons 
namely "submit and return" and "submit and close".  The "submit and 
close" button submits the string, and on the next page there is a 
JavaScript that closes the page.  The "submit and return" submits the 
string, and on the next page is a JavaScript that goes back in history 
(it mimicks the backbutton).

The problems with this hack are:
1. If a user's browser is set up to reload the page always, then even a 
backbutton-script will not prevent the long search page from reloading 
all over again.
2. If a user goes back in history, the segment he has edited will be the 
same as before (the changes he had just made, will not be visible).

For (1) above, well, the user will figure out sooner or later that the 
feature is of no use to him, and he'll stop using it (or figure out 
what's wrong and make the necessary changes to his browser).

For (2), well, I wonder if there is a way to indicate whether a segment 
has been visited.  If the segments had little "Edit" links permanently 
(instead of that mouse-over method that exists currently), those links 
can change colour (visited links versus unvisited links), so that would 
be one way for a user to see which segment he had visited.

> - search and replace

One way a search and replace (with confirmation) may be done, is to take 
the user to the next string (as usual) but to load the changed string 
into the edit box (and put the original string somewhere on the screen 
as well, with the changed word(s) highlighted).  On such a screen, there 
should be only three buttons, and they should be labelled as such: 
"accept this change" (performs a submit), "ignore, go to next change" 
(performs a skip) and "back".  There should be a clear, visual 
indication that the user is busy with a search and replace and what the 
exact current search/replace operation is.

> We should take into account the limitations we have using pogrep
> and/or indexing, eg, pogrep supports regex whereas indexing can't
> perform this kind of searches. In case indexing is enabled on the
> server and an operation can't be done with the indexing engine, we
> should fall back to pogrep.

Or how about this:  the current search option is renamed "quick search" 
or similar.  It remains where it is and it does indexed searches.  Then 
there should be an extra option "advanced search" (a link).  If the user 
clicks it, it opens a new window with a form with multiple search 
options.  It being a separate page with a longer form, users will not be 
miffed if the search takes somewhat longer.

Samuel

-- 
Samuel Murray
[EMAIL PROTECTED]
Decathlon, for volunteer opensource translations
http://translate.sourceforge.net/wiki/decathlon/

-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Search enhancements

2008-07-14 Thread Lars Kruse
Hi Julen,

improving the search interface is a great thing - thanks for your work!

> I've created a wiki page[4] for the purpose, so feel free to
> add/remove/edit any information you see necessary. Lars, you're
> probably the person who better knows this stuff so your help and
> comments would be very welcome.

I added specific points for the indexing support.
http://translate.sourceforge.net/wiki/developers/developers/julen/searching

Hopefully it helps!

regards,
Lars

-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


[translate-pootle] Patch for adding the ability to configure a project l10n directory from pootle admin page

2008-07-14 Thread Suresh Chandrasekharan
Hi All,

(Resending the mail as the original one with a screenshort was held 
due to size restrictions)

   I have posted a patch for configuring the path to Project po/xliff 
directories from the
pootle admin page.

See
http://bugs.locamotion.org/show_bug.cgi?id=452

The patch essentially give the admin the ability to configure the 
already existing project
l10n directory from the admin/projects.html page

The typical use case is like this. An admin who had already checked out 
a few projects
in a server system the Pootle is running would like to configure the 
access to the project
translation directories from admin/projects.html page, he gives the 
absolute path or relative
path from the Pootle/po directory in the 'Project L10N Directory' , then 
the system will
go ahead and will create the needed links from to the project po files 
so that the users will
be able to work on the new project created.

For example when configuring a new project., gedit, I'm giving the path 
to the project
po file path /export/home/user/projects/gnome/trunk/gedit/po in the 
'Project L10N
Directory' field, then the project link will be updated with the .po 
files in that path after
you click on'Save Changes'. You don't have to do this as a combination 
of CLI/GUI
task, but can do this in as a single shot GUI task.

The patch only creates sym link (removes existing symlinks if any) and 
does not do any
deletion of directories.

One concern that I heard in the #pootle channel is that the ability to 
do this will compromise
system security (in case the Pootle system is shared by different admins 
who are hostile
to each other) by somebody who will try out different path combinations 
and get the
access to secret po files which he is not authorized to read... Would 
like to get feedback
regarding this.


Screenshot at
http://bugs.locamotion.org/attachment.cgi?id=167

Regards,
Suresh


-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Search enhancements

2008-07-14 Thread F Wolff
On Ma, 2008-07-14 at 09:09 +0200, Julen wrote:
> Hi everyone,
> 
> Following with my SoC tasks, time for search enhancements has arrived.
> Last Friday Friedel, Clytie and me discussed briefly some ideas on IRC
> and I want to expand the discussion here so we can define the right
> way to go.

Great to hear of all the progress!

> There are already some RFEs on this topic[1] [2] [3], claiming these
> improvements:
> - searching for specific fields (source, target, notes, locations)
> - case-sensitive searches
> - regex. support
> - listing all the search results in a single page
> - choosing the hierarchical point to search in
> - recent searches
> - search and replace
> 
> As you can see there are a bunch of things to improve, but for now we
> should prioritize the most important things to do.
> I think searching for specific fields is a good starting point, which
> could lead to major improvements in the future.

I think we need to realise that our rules for prioritisation is
influenced by at least the usefulness _and_ the amount of work to
implement an improvement. Doing specific fields should be fairly easy,
and I guess that is part of why I support this as a starting point.

> 
> We should take into account the limitations we have using pogrep
> and/or indexing, eg, pogrep supports regex whereas indexing can't
> perform this kind of searches. In case indexing is enabled on the
> server and an operation can't be done with the indexing engine, we
> should fall back to pogrep.
> I've created a wiki page[4] for the purpose, so feel free to
> add/remove/edit any information you see necessary. Lars, you're
> probably the person who better knows this stuff so your help and
> comments would be very welcome.
> 
> Looking forward to your comments,

Instead of just falling back to pogrep, we could use the results from
the indexing and filter through the results to implement the same
effect. In fact, we might be able to build a fake translation store with
all the search results, and then use pofilter to search through that. It
should still be faster than using pofilter directly on all the files -
which can be very slow in large projects.

I'll try to add some extra notes to the wiki page.

Friedel


-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Support for XML based Java properties files

2008-07-14 Thread Dwayne Bailey
On Fri, 2008-07-11 at 13:19 +0200, maneo wrote:
> Hi!
> 
> I read about Pootle and translation toolkit I'm thinking about using 
> Pootle to translate my application. I have a lot of short XML based 
> Java-properties files which includes different language versions. eg.

Glad to see your looking and Pootle and hope we can get you onboard :)

> example_pl.xml:
> 
> 
> http://java.sun.com/dtd/properties.dtd";>
> 
>UTF8
>Identyfikator
>wprowadz
> 
> 
> We decided to use xml properties files because sometime we have store 
> information about multiline text segments. Standard .properties version 
> alows only to store one-liners.

I think \ allows you do do multilines.  Its used in Mozilla .properties
files for certain.

> I've read that Pootle support Java .properties files. My question is, do 
> you know any tools which alow to import XML based Java properties files 
> (like example above) into Pootle workflow? Maybe there is something 
> which alows for simple conversion between xml-properties and XLIFF ?

I haven't seen anything I'm afraid.  You might want to look at the
Gettext tools which can manage .propeties files.  This might give you
the ability to get them into .po format and then you can use Pootle.

Please let us know what you discover.

> 
> kind regards,
> Adam
> 
> -
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> ___
> Translate-pootle mailing list
> Translate-pootle@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/translate-pootle
-- 
Dwayne Bailey
Managing Director   +27 12 460 1095 (w)
Translate.org.za+27 83 443 7114 (c)


-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


Re: [translate-pootle] Viewing suggestions while translating

2008-07-14 Thread Julen
We've setup beta.locamotion.org with this code so it's easier for you
to test it. Feel free to check it out :)

Cheers,

Julen.

-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle


[translate-pootle] Search enhancements

2008-07-14 Thread Julen
Hi everyone,

Following with my SoC tasks, time for search enhancements has arrived.
Last Friday Friedel, Clytie and me discussed briefly some ideas on IRC
and I want to expand the discussion here so we can define the right
way to go.

There are already some RFEs on this topic[1] [2] [3], claiming these
improvements:
- searching for specific fields (source, target, notes, locations)
- case-sensitive searches
- regex. support
- listing all the search results in a single page
- choosing the hierarchical point to search in
- recent searches
- search and replace

As you can see there are a bunch of things to improve, but for now we
should prioritize the most important things to do.
I think searching for specific fields is a good starting point, which
could lead to major improvements in the future.

We should take into account the limitations we have using pogrep
and/or indexing, eg, pogrep supports regex whereas indexing can't
perform this kind of searches. In case indexing is enabled on the
server and an operation can't be done with the indexing engine, we
should fall back to pogrep.
I've created a wiki page[4] for the purpose, so feel free to
add/remove/edit any information you see necessary. Lars, you're
probably the person who better knows this stuff so your help and
comments would be very welcome.

Looking forward to your comments,


Julen.

[1] http://bugs.locamotion.org/show_bug.cgi?id=336
[2] http://tinyurl.com/6mxv4j
[3] http://tinyurl.com/6pzlln
[4] http://translate.sourceforge.net/wiki/developers/developers/julen/searching

-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle