Since there's no way to automate the process, any translators that are following a certain language will have to update manually by watching the changes. I wish it could be otherwise.
If nobody has any objections, I'm pushing the "branch" button ;)
From now on, let's write for .47
Some things to be careful of: let's be sure a new feature is really going to be in the next release before spending much time on it, and let's make sure that the details of a new feature are finalized before we finalize our documentation of such features :)
JF
Alexandre Prokoudine wrote:
On Wed, Mar 25, 2009 at 5:49 PM, Alexandre Prokoudine wrote:
On Wed, Mar 25, 2009 at 12:16 PM, C�dric G�my wrote:
I agree this is THE choice. 0.47 is pretty coming soon, and there are some huge work to do on new stuffs improving old tools (pen...). These are very visible options and i think this should be completely documented first.
We could aim at having an uptodate FM manual as soon as possible, even if not daeling with the whole software( but was it already the case with 0.46 ?)
If there are no objections, somebody has to press the branching button :)
Just one question: what will happen to translations after branching?
Alexandre
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs