On Thu, Nov 15, 2012 at 11:53 PM, Andras Timar <timar74@gmail.com> wrote:
Perhaps fully cloning projects (with suggestions and other stuff) would
be a
valid feature request for Pootle? :)
Yes, it would. I wanted to clone last time, and I learned that it was
not possible. But I forgot this feature request and did not mention it
to Dwayne at LibOCon. I was convinced that maintaning two branches
with suggestions may be a pain for most of the teams. I think about
the stable branch as it is for fixing annoying translation bugs only,
and the newer branch is for the real work. If a team could not finish
3.6.x translations by now, maybe it's time to go for 4.0 instead. So,
I would not mind, if cloning was possible, but I would give higher
priority to some other feature requests. What do others think?
I would ask anyway, but state it has lower priority for us. Worst case, it
will just be an item on their wish list.
And I think that after we finish with the 3.6.4 update, there's no point of
continuing translation that branch, and focus should be moved completely to
the 4.0 branch.
Kaplan
--
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.