<div dir="ltr">Hi there,<div>I'm actually all for IRC and freenode in particular, though #www-team is a rather unfortunate choice as its quite the name-grab and does not really comply with the (admittedly, informal) channel naming policy (to be found at <a href="http://freenode.net/policy.shtml#channelnaming">http://freenode.net/policy.shtml#channelnaming</a>). A better name would perhaps be #tor-wwwteam :)</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 7, 2014 at 11:17 PM, Rey Dhuny <span dir="ltr"><<a href="mailto:rey@spcshp.com" target="_blank">rey@spcshp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Just as an aside, I'm idling in #www-team on Freenode if anybody else wants to join.<div><br></div><div>It's on Freenode because I'm connected already anyway, if there's a Tor project preferred network/channel (<a href="http://irc.oftc.net" target="_blank">http://irc.oftc.net</a>, perhaps?) please let me (and the mailing list!) know so we can get involved.</div>
<div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Tue, Jan 7, 2014 at 8:48 PM, Simeun Furtula <span dir="ltr"><<a href="mailto:simeunf@gmail.com" target="_blank">simeunf@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
It looks like Middleman fulfills all requested technical requirements except the feature that would allow translation teams to be informed about obsolete content. It would be silly to expect such a feature from a software that is primarily a *static site generator*. Middleman itself *is* a static site generator. It uses markdown documents for storing content, which makes translation work a lot easier than it is now. Also, it supports localization out of the box, which makes it a very good choice.<br>
<br>
As git is going to be used for storing content, I assume it wouldn't be hard to build/setup separate system which will take care of translations, and make life easier for content translators. Anyway, main features of such tool should be:<br>
- to allow easy translation of content (plain simple editing of markdown documents)<br>
- to allow easy translation of language files (Middleman uses YAML, which doesn't require much technical knowledge to edit)<br>
- to notify translators of changes in content of "main" language (English?)<br>
<br>
I don't know if any of such tools exists, although I believe there is a plenty of them. If someone knows of a such software packet, please let me know.<br>
<br>
+1 for Middleman blogging support<br>
<br>
Best regards,<br>
Simeun<div><div><br>
<br>
On 1/7/2014 9:21 PM, Frithjof wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On Tue, Jan 7, 2014 at 9:04 PM, Rey Dhuny <<a href="mailto:rey@spcshp.com" target="_blank">rey@spcshp.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hopefully we can come up with a system for i18n better than WML. Looks like<br>
we have a couple guys with experience in the group.<br>
<br>
Middleman does localisation out the box:<br>
<a href="http://middlemanapp.com/advanced/localization/" target="_blank">http://middlemanapp.com/<u></u>advanced/localization/</a><br>
<br>
</blockquote>
I think the real problem here is not 'having a backend that can handle<br>
multiple languages',<br>
but 'how can one store and edit translations in such a way, that<br>
<br>
* translation teams are informed about obsoleted parts of their pages, and<br>
* people with little knowledge about web development can edit the translations.<br>
<br>
--Frithjof<br>
______________________________<u></u>______________________________<u></u>____________<br>
Tor Website Team coordination mailing-list<br>
<br>
To unsubscribe or change other options, please visit:<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team" target="_blank">https://lists.torproject.org/<u></u>cgi-bin/mailman/listinfo/www-<u></u>team</a><br>
.<br>
<br>
</blockquote>
<br>
______________________________<u></u>______________________________<u></u>____________<br>
Tor Website Team coordination mailing-list<br>
<br>
To unsubscribe or change other options, please visit:<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team" target="_blank">https://lists.torproject.org/<u></u>cgi-bin/mailman/listinfo/www-<u></u>team</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div dir="ltr"><div><a href="http://reyhan.org" target="_blank">reyhan.org</a></div></div>
</font></span></div></div>
<br>________________________________________________________________________<br>
Tor Website Team coordination mailing-list<br>
<br>
To unsubscribe or change other options, please visit:<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team</a><br>
<br></blockquote></div><br></div>