headers
Richard Liao | 9 May 10:15
Picon

[Trac-dev] Re: branch merge: i18n


I have posted this message in another thread.
Please ignore above.

2008/5/9 Richard Liao <richard.liao.i <at> gmail.com>:
> Hi,
>
> I'm trying to make a fully translated trac 0.12 based on the trunk(r7002).
>
> What I have done:
> 1. Fully translated the messages.po file.
> 2. Fully translated the default wiki pages into our local language: zh_CN.
>  (I have noticed new help branch in sandbox, but currently, I have to
> translate these wiki pages.)
>
> The problem is: the UI elements are not fully i18n-ed.
> 1. Some string is not i18n-ed in py files.
> e.g.
> trac/ticket/web_ui.py: line 308:309
>           return tag('Ticket ', tag.em('#', ticket.id, title=title),
>                      ' (', shorten_line(summary), ') ', verb)
> those should be:
>           return tag(_('Ticket '), tag.em('#', ticket.id, title=title),
>                      ' (', shorten_line(summary), ') ', _(verb))
> How do I submit a patch?
>
> 2. Some strings never appear not in genshi template or py files:
> e.g.
>  trac/ticket/template/ticket.html: line 150
>                 <py:if test="field">${field.label or field.name}:</py:if>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Liao | 9 May 05:54
Picon

[Trac-dev] make i18n practicable


Hi,

I'm trying to make a fully translated trac 0.12 based on the trunk(r7002).

What I have done:
1. Fully translated the messages.po file.
2. Fully translated the default wiki pages into our local language: zh_CN.
 (I have noticed new help branch in sandbox, but currently, I have to
translate these wiki pages.)

The problem is: the UI elements are not fully i18n-ed.
1. Some string is not i18n-ed in py files.
e.g.
trac/ticket/web_ui.py: line 308:309
            return tag('Ticket ', tag.em('#', ticket.id, title=title),
                       ' (', shorten_line(summary), ') ', verb)
those should be:
            return tag(_('Ticket '), tag.em('#', ticket.id, title=title),
                       ' (', shorten_line(summary), ') ', _(verb))
How do I submit a patch?

2. Some strings never appear not in genshi template or py files:
e.g.
 trac/ticket/template/ticket.html: line 150
                  <py:if test="field">${field.label or field.name}:</py:if>

 and in  trac/ticket/web_ui.py: line 552:560
 the string of ticket.fields['label'] or ticket.fields['edit_label']
or ticket.fields['name'] is not i18n-ed.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Jeroen Ruigrok van der Werven | 8 May 14:58
Gravatar

[Trac-dev] attachment notification


Did 0.10 notify when someone attaches a file to a ticket? So, just an
attachment, no comment.

If so then current behaviour of 0.11 regressed, if not, then we really need
to get an option for it. ;)

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
If Winter comes, can Spring be far behind..?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 2 comments |
headers
Justin T. Gibbs | 2 May 19:57

[Trac-dev] trac-xref branch - any plans?


Hi,

It seems that the trac-xref branch has been idle for some time.
Is there still general interest (other than my own) for this
feature?  Are there already plans to integrate it into a future
release?

Thanks,
Justin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
Jeroen Ruigrok van der Werven | 3 May 11:44
Gravatar

[Trac-dev] tentative 0.12.0 release schedule


My current suggestion:

beta 1 : 2008-10-01
beta 2 : 2008-10-14
rc1    : 2008-11-01
rc2    : 2008-11-14 (as needed)
release: 2008-12-01

And a suggestion aside from the above:

2008-[06/07/08/09]-01 we will use for creating tech previews (which we will
update t.e.o. with) for showcasing the current state of Trac.

My main reason for being a bit 'strict' on the dates is that it would give
us early feedback of trunk's behaviour on large datasets and tackle any
blocker issues like the memory problem early on.

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Knowledge is power...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 5 comments |
headers
Christian Boos | 2 May 11:42
Picon
Favicon

[Trac-dev] SpamFilter on t.e.o


Hi Jonas,

First, I've noticed that we have now: [spam-filter] min_karma 0
Wasn't that higher in the past, like "3"? "1" should be the minimum, I 
think (and this would have caught those stupid "haha;" comments from 
this morning...).

Also, there's still the problem with the unicode or binary attachments 
(#5591). This is becoming increasingly annoying for the translators.
Last time I've tried to reproduce it locally with PostgreSQL (8.1 win32, 
accessed through psycopg2 2.0.6), I couldn't, so I think this is 
something best debugged on t.e.o itself.

Now that I'm talking about the spam-filter, I should mention that I've 
revived the spam-filter-captcha variant from Alec, and modulo one last 
change I'd like to make (#7173) I think it would be good to integrate it 
back in the "main" spam-filter plugin. We could then eventually enable 
it on t.e.o as well (but that's really a separate question).
What do people think?

-- Christian

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 3 comments |
headers
Christian Boos | 2 May 10:17
Picon
Favicon

[Trac-dev] /branches/0.11-stable write permission access


Hi Jonas,

It seems I don't have the write permission there.
Please add it for me and others.

Also, you could take this opportunity to kill the old developer-specific 
branches (cboos-dev, cmlenz-dev, etc.). Christopher was OK with that.

-- Christian

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 5 comments |
headers
Ted Gifford | 1 May 16:13
Picon

[Trac-dev] Patches I use


Here's two patches I use that I don't see in trunk. Is it better to 
submit them in the tracker?

1. I mentioned this one in trac-users. It redirects to the raw download 
for attachments that aren't rendered (wiki probably isn't the best 
section of config...)

--- c:\tracdev\trac\trac\attachment.py    2008-04-30 16:50:48.833972400 
-0400
+++ C:\Python25\lib\site-packages\trac\attachment.py    2008-04-30 
16:53:08.910304400 -0400
@@ -399,6 +399,9 @@
             data = self._render_form(req, attachment)
         else:
             data = self._render_view(req, attachment)
+            if self.env.config.get('wiki','forward_to_raw_href') and 
data['preview']['rendered'] is None:
+                req.redirect(data['preview']['raw_href'])
+                return # cancel all template processing

         add_stylesheet(req, 'common/css/code.css')
         return 'attachment.html', data, None

2. Added data argument to match post_process_request api, and pass None 
for post_process requests arguments.

--- c:\tracdev\trac\trac\versioncontrol\api.py    2008-04-30 
16:50:43.740287600 -0400
+++ C:\Python25\lib\site-packages\trac\versioncontrol\api.py
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jeroen Ruigrok van der Werven | 30 Apr 21:48
Gravatar

[Trac-dev] branch merge: i18n


People,

since 0.11 has been branched trunk is now 0.12-dev material.
Given the fundamental nature of a framework like i18n into any given
software project I want to merge this in as soon as possible. This will make
sure that markup and extraction can be dealt with immediately. Also more and
more users have been using the sandbox to deploy Trac in their native
language.

The patchset is reasonably small at this point:

http://trac.edgewall.org/changeset?new=6944%40sandbox%2Fi18n&old=6942%40trunk

Let me know of any objections or otherwise.

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Light, a quark resolution of god...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 18 comments |
headers
anatoly techtonik | 27 Apr 17:08
Picon

[Trac-dev] wiki renderer web-service for testing


Hello, everybody

Is it possible to expose wiki renderer interface for Trac into POST
web-service? I'll be grateful if anybody with core knowledge could
provide a small patch. It will be useful for unit testing of renderer
and in my specific case for running test for a small wiki converter.

Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
Emmanuel Blot | 25 Apr 23:49
Picon

[Trac-dev] t.e.o. unstable ?


I just encountered two major issues while browsing on t.e.o. within a
single minute time frame:

1/ When I clicked on "View Ticket/Custom Query" I got a Python
traceback (plain text, no decoration) reporting that "layout.html" was
missing. A simple refresh made the trouble go away.
2/ In the custom query report, I clicked on the ticket column header
(to sort result by ticket number) and I hit a "500 Internal Error" web
page. Again, a refresh made the trouble go away.

It happened at 23:47 CET (GMT+1), if someone wants to have a look at
the log files.

Cheers,
Manu

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 3 comments |

Gmane