[libreoffice-l10n] LibreOffice Bugzilla Migration is happening January 24th -- read on for more details!
But first: Happy New Year, everyone! https://colonelqubit.wordpress.com/2014/12/31/happy-new-year-libreoffice/ THE MIGRATION: The QA Team and the wonderful admins over at Freedesktop.org have been working hard to prepare for the migration of our LibreOffice bugs to TDF infrastructure. I'm happy to announce that we'll begin the migration on January 24th at 15:00 UTC. For all kinds of details about the migration (as well as a whimsical picture of our friendly walrus mascot in his Bugzilla-testing outfit), point your browser here: https://colonelqubit.wordpress.com/2014/12/31/mark-your-calendars-libreoffice-bugzilla-migration-is-1-month-away/ QUICK DETAILS: - Migration Date: January 24th, 2015 at 15:00 UTC - Migration Duration: Approximately 4-6 hours - New URL: https://bugs.documentfoundation.org/ - Purpose: Migration will give us increased flexibility to extend Bugzilla, integrate other TDF services, and provide granular support for diverse tools including the Impress Remote and the Document Liberation Project. **Please Note**: For your security, all passwords will be reset as a part of the migration process. The first time you visit the site, click the 'Forgot Password' link and follow the instructions to set a new password. During the migration, Bugzilla will be *inaccessible*, but you may join us in the #libreoffice-qa channel on Freenode or on the QA Mailing List at any time during or after the migration for up-to-date information about our progress. You can also just stop by to say hi! MORE INFORMATION: For more information, please see my blog post (above) and the Migration Userguide: https://wiki.documentfoundation.org/QA/Bugzilla/TDF_Bugzilla_Proposal/Migration_Userguide#Guide If you have any questions about the migration, feel free to email me or the QA mailing list: https://wiki.documentfoundation.org/QA/Mailing_List Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Reminder: LibreOffice Bugzilla Migration will happen next Saturday (Jan 24th)
Hi all, I hope that winter has been treating you well! This is just a quick reminder that we'll be migrating all of the LibreOffice bugs from Freedesktop.org to https://bugs.documentfoundation.org/ this coming Saturday. REMEMBER: You *WILL* have to reset your password after the migration is complete. KEY DETAILS: - Migration Date: January 24th, 2015 at 15:00 UTC - Migration Duration: Approximately 4-6 hours - New URL: https://bugs.documentfoundation.org/ - Information about the migration: https://wiki.documentfoundation.org/QA/Bugzilla/TDF_Bugzilla_Proposal/Migration_Userguide#Guide As always, if you have any questions about the migration, feel free to email me or the QA mailing list: https://wiki.documentfoundation.org/QA/Mailing_List Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] [LibreOffice Bugzilla Migration] Starting shortly! Bugtracker will down for a few hours
Hi all, It's that time! We're just about to migrate Bugzilla from Freedesktop.org to TDF infrastructure. For up-to-date information about the migration, join the #libreoffice-qa IRC channel on Freenode and say hi! For general information, see https://wiki.documentfoundation.org/QA/Bugzilla/TDF_Bugzilla_Proposal/Migration_Userguide#Guide KEY DETAILS: - Migration Date: January 24th, 2015 at 15:00 UTC - Migration Duration: Approximately 4-6 hours - New URL: https://bugs.documentfoundation.org/ Once the migration is complete, I'll send out another email letting you know you may once again ply us with myriad bug reports :-) Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] [LibreOffice Bugzilla Migration] We're done! Please visit the new site to reset your password!
Hi everyone!
The migration was a great success. All of our bugs are now happily living at
https://bugs.documentfoundation.org/
Bugs should be referenced using the shorthand tdf#, such as tdf#12345.
On the wiki, you can write {{tdf|12345}} to link to a bug report.
Before you can log-in and start working on bugs, you'll need to reset
your password. Read more here:
https://wiki.documentfoundation.org/QA/Bugzilla/TDF_Bugzilla_Proposal/Migration_Userguide#After_the_Migration
If you have any questions or encounter any problems, please stop by
the QA IRC channel or drop us a note on the mailing list:
https://wiki.documentfoundation.org/QA/IRC
https://wiki.documentfoundation.org/QA/Mailing_List
A huge thanks to everyone who helped make this migration go quickly
and smoothly! Let's go tackle some open bugs!
Cheers,
--R
P.S. You'll start to see some updates and changes in Bugzilla over the
coming weeks. The QA Team is excited to work on improving, updating,
and polishing our bugtracker. We're always happen to have more people
join us!
--
Robinson Tryon
QA Engineer - The Document Foundation
LibreOffice Community Outreach Herald
qu...@libreoffice.org
--
To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Fwd: [tdf-announce] LibreOffice Viewer (Beta) now available for Android
On Mon, Jan 26, 2015 at 10:49 AM, Sophie wrote: > Le 23/01/2015 20:03, Valter Mura a écrit : >> is there any translation plan for the app below mentioned? > > Currently the strings of the viewer are part of the main code, so no > need for translations. Is there a way to pick a different language from inside the Viewer, or does it just choose whatever language is set at the OS-level? Thanks, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Re: Workflow between dev, UX and l10n teams
On Tue, Jan 27, 2015 at 5:43 PM, Wols Lists wrote: > Am I right in reading into this, that master is using American English? > And if so, why? Seeing as LibreOffice is, at heart, a European program > surely it should be using English? Like British English? RP? Let's be specific here... > > What proportion of developers are native American speakers? Not that many. It would be great to see more involvement from the US, but I think that promoting the "this is a European Project" attitude can really hurt those numbers. LibreOffice is a global project: No one country or continent should try to claim it for itself. > Bear in mind that most English variants use English spelling, not > American spelling. I think the phrase "American English spelling" is clearer -- there are lots of languages spoken here across the pond, so the phrase "American spelling" is ambiguous. > At the end of the day, not enforcing en_us as a translation means that > the majority of us (including those of us that speak English rather than > American as our native language) are forced to suffer pain as the > foundations are messed up underneath us. Whoa there, cowboy! (or whatever the British equivalent is) I think that British, American, Canadian, etc.. English are all pretty similar, so while I agree that we might have our little differences about an extra 'u' in color, or whether the big vehicle that picks up the trash is a Lorry or a Truck, it's not a big deal compared to the diff between the Englishes and French or Spanish. > And by allowing that *minority* > to avoid suffering, they are enabled to cause unnecessary pain without > even realising what they are doing! *facepalm* I know that you're just getting some stuff off your chest, and sure, I get it: languages can be tough. So we get have a couple beers, find the vertias in the vino, and start speaking French (wait, maybe that's just what I do). More seriously, I'm trying to get people interested in LibreOffice in the US, and it's really important for us to make the project welcoming to users and new contributors. You want to propose some changes? Sure, great plan. But please check that your method of delivery doesn't paint the Americans as the outsiders and buffoons of your diatribe, because the reality is that we really don't have much going on in the US yet, and there's already a hesitancy to interact with what is perceived as aloof Europeans. I think that growth in the US has the potential to give a ton back to the LibreOffice community in Development, Documentation, QA, and so forth, but we need to go the extra mile there, not tell people that, before they've opened a single spreadsheet or triaged a single bug, they are somehow (?) "causing pain." > The rule should be simple. Any changes of meaning can be edited directly > in master. If it's non-native English, and poor at that such as it's > hard to comprehend then it can be corrected in master. If it's clear > comprehensible English, whether English or Strine or American or > International or whatever, then it's off-limits for changes to master, > and has to be done in Pootle or whatever as a localisation. I like the general idea, but I am concerned about the feasibility. Notes: 1) will inconsistency of nouns (e.g. color vs. colour), inconsistency of grammar, etc.. within the sources in master make translation harder for the native-lang teams? 2) What will the language be for builds w/o langpacks? Just a generic 'English'? (maybe we can call it "LibreOffice English" :-) 3) Who's going to step up to maintain en_US? (I'd love to help, but I'm working tons of hours as it is) Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] LibreOffice 4.4.4 RC1 available
Dear Community, The Document Foundation is pleased to announce the first release candidate of LibreOffice 4.4.4. The upcoming 4.4.4 will be the first in a sequence of frequent bugfix release for our feature-packed 4.4 line. Please be aware that LibreOffice 4.4.4 RC1 is not been flagged as ready for production use yet, however feel free to give it a try instead of 4.4.3. A work-in-progress list of new features in LibreOffice 4.4 can be found at https://wiki.documentfoundation.org/ReleaseNotes/4.4 The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Developers and QA might also be interested in the symbol server for windows debug information (see the release notes linked below for details) Should you find bugs, please report them to our Bugzilla: https://bugs.documentfoundation.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/community/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs with 4.4.4 RC1 is available from our wiki: http://wiki.documentfoundation.org/Releases/4.4.4/RC1 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. On behalf of the Community, Robinson -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org 802-379-9482 | IRC: colonelqubit on Freenode -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] LibreOffice 5.0.1 RC2 available
Dear Community, The Document Foundation is pleased to announce the second release candidate of LibreOffice 5.0.1. The upcoming 5.0.0 will be the first bugfix release of our fresh 5.0 line. Please be aware that LibreOffice 5.0.1 RC2 has not been flagged as ready for production use yet, however feel free to give it a try instead of 5.0.0. A work-in-progress list of new features in LibreOffice 5.0 can be found at https://wiki.documentfoundation.org/ReleaseNotes/5.0 The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Windows builds are also provided in 64bit version. Should you find bugs, please report them to our Bugzilla: https://bugs.documentfoundation.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/community/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs compared to 5.0.1 RC1 is available from our wiki: http://wiki.documentfoundation.org/Releases/5.0.1/RC2 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help! --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org 802-379-9482 | IRC: colonelqubit on Freenode -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] LibreOffice 5.0.2 RC1 available
Dear Community, The Document Foundation is pleased to announce the first release candidate of LibreOffice 5.0.2. The upcoming 5.0.2 will be the second bugfix release of our fresh 5.0 line. Please be aware that LibreOffice 5.0.2 RC1 has not been flagged as ready for production use yet, however feel free to give it a try instead of 5.0.1. A work-in-progress list of new features in LibreOffice 5.0 can be found at https://wiki.documentfoundation.org/ReleaseNotes/5.0 The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Windows builds are also provided in 64bit version. Should you find bugs, please report them to our Bugzilla: https://bugs.documentfoundation.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/community/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs compared to 5.0.1 final (rc2) is available from our wiki: http://wiki.documentfoundation.org/Releases/5.0.2/RC1 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. Cheers, Robinson -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org 802-379-9482 | IRC: colonelqubit on Freenode -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Re: [libreoffice-documentation] Video Tutorial Link in Help
Sophie wrote: >> What we do not want in localised version is content in en_US language. >> Even if the sound is translated, UI still will be in English and it's >> very difficult to focus on what you learn when all what you see is in >> a foreign language. In terms of the content that we provide on a per-language basis, I agree that it's important to be able to provide consistency to those users who desire it. For those who wish to see only content in language XYZ, then we should strive to show them only content in XYZ. On Wed, Dec 9, 2015 at 4:31 PM, Joel Madero wrote: > Just for full transparency here. Sophie and I had an extended talk on > chat and I'm of the belief that to prevent this from getting into help > files because other locales aren't doing the same is not the smartest > way to move forward. I instead would prefer including it and then > supporting locales to do the same - in the respective languages, with > the right GUI, etcThese then would be linked in the locales help > files and it would empower the community, expand on the product, and > give visibility to a great tool (videos that literally show exactly how > to use features). For those who are multilingual or just adventurous, I can see the potential benefit if users could choose on a program-wide level to toggle on extra non-localized content (let's call it "Extended Documentation") for each page of the Help. If we were to have rather stringent rules about what content (format, length, structure, license, etc..) could be included in this fashion, then we'd have a decent roadmap on what content we'd like to see localized next. If we're clever about how we include Extended Documentation, we could even recruit for translation/localization by adding a small message to any non-localized content such as "Want to see this content in $CURRENT_LOCALE? Click here to help out!" > I'd prefer discussing a better solution, one where we can agree that the > tool is awesome for users, that the more visibility the better, and one > that empowers contributors to follow Robert's lead and developer > tutorial videos in their respective languages. I'd suggest that any video content included or linked from the Documentation be provided in a similar fashion to our existing text content. Off the top of my head, this would include: - Licensing under CC-BY or CC-BY-SA 3+ - Use of free/open file formats - "Source" video archived safely somewhere in TDF infra - Inclusion of extra source materials (e.g. talking points used to make the video, example docs displayed or demonstrated during the video, etc..) with the archived source video to help others who may wish to edit or reshoot the content - Ability to Download or view video using only Free Software (Archive.org?) - Strong encouragement for any cross-platform content to be demonstrated using the Doc Team's preferred Free Software GUI shell [1] It would be great to have subtitles provided for each source video from the get-go, however that's definitely a task that can be handled independently, freeing up video creators to create more videos... Cheers, --R [1] https://wiki.documentfoundation.org/Documentation/Production#Sample_screenshots Also see: https://en.wikipedia.org/wiki/Wikipedia:Software_screenshots -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org 802-379-9482 | IRC: colonelqubit on Freenode -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Wikihelp/Help Wiki/Online Help/etc... needs one clear name
[Sophie suggested that I ping this list regarding the Wiki Help...] Hi all, I've been doing some QA prep work for our upcoming Bugzilla migration and I've noticed that we have a few different names for the same online help/wiki resource, and that's confusing. I suggest that we pick one name and standardize on it everywhere. Here are a sampling of some of the names and examples of their use: => Wikhelp/WIKIHELP This one is used on the wiki and in the bugtracker: https://wiki.documentfoundation.org/Development/Wikihelp https://wiki.documentfoundation.org/QA/Bugzilla/Components/Documentation/Extended_Help => Wiki Help This one is in the Template:Menu on the wiki: https://wiki.documentfoundation.org/Template:Menu => The Help Wiki Mentioned in the blurb for the 'Documentation' component in Bugzilla: https://bugs.freedesktop.org/enter_bug.cgi?product=LibreOffice&bug_status=UNCONFIRMED&component=Documentation => Online Help This name is given on the wiki, alongside "Wikihelp": https://wiki.documentfoundation.org/Website/Web_Sites_services => LibreOffice Help The menu option in LibreOffice itself (Help -> LibreOffice Help). The help site itself (main page) in the form "LibreOffice Help" and "Welcome to LibreOffice Help!" => LibreOffice Application Help This help site itself (main page) - "Thank you for using the LibreOffice application help" --- One of the issues with the term 'wiki' is that it's very generic. We have our "regular" wiki at wiki.documentfoundation.org, but we don't call it the TDF wiki or the LibreOffice Wiki[1], we just call it "the wiki," which makes the term "Wikihelp" slightly more ambiguous, especially for newcomers to the project. Some people might think the name "Wikihelp" refers to help for our wiki. Some might guess from the name that it's a generally-editable wiki. But neither are true. The term "Online Help" avoids the term "wiki," but I feel like it could be a bit more descriptive. A couple of ideas off the top of my head: * Online Help Pages * Online Help Reference Because we use the same content to generate the local help, it would behoove us to choose a name that conveys that connection, e.g. Online Help Pages -> Local Help Pages We want users to instantly recognize that what they're looking at online is related to what they have available inside LibreOffice (and vice-versa). We could further emphasize that connection by differentiating the names in logos/etc: ONLINE Help Pages -> LOCAL Help Pages In LibreOffice itself, the menu option could be "LibreOffice Help Pages." Thoughts? Cheers, --R [1] To be fair, the front page of the wiki does say "Welcome to the wiki of The Document Foundation", however I've heard "LibreOffice Wiki", "TDF Wiki", and "the Wiki", with the last term being the most prevalent. -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Wikihelp/Help Wiki/Online Help/etc... needs one clear name
On Thu, Nov 14, 2013 at 3:37 AM, Martin Srebotnjak wrote: > Hi, > > "online help" refers to built-in help and the term is not very telling. > Technically speaking I would think more of something like "embedded" or > "included" or whatever the proper English word might be. "local" is very > strange, especially if one day LO will become also a webservice. It will not > be "local" but it will be part of the package, "embedded"; if it won't be > there, there will probably be linking to the wiki, I guess. > "internal"/"external"? I think that the dichotomy between local (included, embedded, built-in, offline, internal) help and online (remote, external) help is mostly clear to the users, although perhaps we could choose those words more carefully. I would like to see a unique name for this online/offline assistance beyond just "Help". I'd recommend a name that we can use to brand this resource so that users will identify it whether it's built-in to LibreOffice or whether it's being accessed online -- something like "Help Pages", "QuickHelp", "LibreHelp", or etc... Cheers, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Wikihelp/Help Wiki/Online Help/etc... needs one clear name
On Thu, Nov 14, 2013 at 5:45 AM, Martin Srebotnjak wrote: > I am looking at it from l10n perspective. "Online help" in most languages > means help online, on the web. While it is actually meant as > embedded/"inline"/offline help. So I just hope all translators translated it > properly. So maybe English names for it should be chosen carefully also for > non-native English speakers. Yes, I agree completely that the name should try to avoid confusion in other languages. Perhaps it would be more clear if we treat the name as a proper noun, the way we do with 'LibreOffice', and not translate it. So "LibreOffice QuickHelp is available online or as a downloadable add-on" would become (in my very poor French) "On se trouve << LibreOffice QuickHelp >> en ligne ou on peut le telecharger". Cheers, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Wikihelp/Help Wiki/Online Help/etc... needs one clear name
On Thu, Nov 14, 2013 at 4:28 PM, Martin Srebotnjak wrote: > Today wiki or embedded help are both quick (unless one uses a phone line > and a modem for Internet access) and contain same information, so naming > one Quick would really not help differentiating them, I guess. Hi Martin, I think Tom's suggestion was that we use the term "QuickHelp" (localized) to refer to the content, and use terms like "internal"/"external" to refer to their location vis-a-vis the user's system. e.g. If I access the QuickHelp locally on my (en-US) system, it would be branded/referred to as "Internal QuickHelp". If I access it online, it would be "External QuickHelp". If Sophie access the QuickHelp locally on her FR system, it could be branded/referred to as "AideRapide Interne", and online as AideRapide Externe". Cheers, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Wikihelp/Help Wiki/Online Help/etc... needs one clear name
On Thu, Nov 14, 2013 at 4:45 PM, Martin Srebotnjak wrote: > Ok, got it. But Quick is really not necessary, isn't "LibreOffice Help" or > just "Help" (where Help gets localized) enough? Personally, I think the term "Help" or "LibreOffice Help" is ambiguous. I wish there were a term for those-help-files-included-in-an-application, but I don't think one exists :-) I think the reason that we've referred to this particular resource using so many different terms (per my original email) is *precisely* because the term 'Help' is so generic. People don't want to leave it naked, and so try to add descriptive terms to it in order to inform the user and guide him to the proper content. > Branding something with a very special name that should be a part of every > serious office suite is strange. > Next we will rebrand "dialogs" with "NiceDialogs" and "context menus" with > "HelpfulContextMenus"? The terms "dialog" and "context menu" are extremely unambiguous in the context of LibreOffice. The term "help" is used all over the place -- we even have a jumping-off page called "get-help": https://www.libreoffice.org/get-help --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Wikihelp/Help Wiki/Online Help/etc... needs one clear name
On Thu, Nov 14, 2013 at 5:24 PM, Sophie Gautier wrote: > > There use to be some non ambiguous terms: > help for help files > support for support > guides, how-to, faq... for documentation > This is still the used terms for a lot of users whatever the localization. > Why not fit to that? +1 My big focus is standardization. I just want to have one consistent name across the board. >> ... The term "help" is used all over the place -- >> we even have a jumping-off page called "get-help": >> https://www.libreoffice.org/get-help > > Which would be /get-support > I don't want to minimize what the help files are, I know several countries > without connection where it's the only documentation, for other countries, > these files are the only legal documentation we can provide. For most of the > users 'help' is understood as the help files shipping with the product. I > won't change that but the other terms we use on the site, etc... Yep, sounds good to me :-) --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Untranslated strings in verson 4.1
On Thu, Nov 14, 2013 at 5:25 PM, Olivier Hallot wrote: > Em 14-11-2013 19:16, Andras Timar escreveu: >> Well, these strings have been there since 2002, and nobody cared, if >> they were localized. :) I would leave them alone. > > I don't follow you... It hurts when I show LibreOffice capabilities and > I step into an untranslated dialog. This is not good for LibreOffice. I think Andras' point was that we could probably punt (until the next cycle) the addition of translations for strings rarely seen by end-users; string- and code-freezes help us to keep our sanity :-) --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Quality in l10n
On Mon, Dec 2, 2013 at 1:03 PM, Sophie wrote: >>> Although the origin of the english strings are from the developers, >>> and they are focused in producing code and fixing bugs more than >>> writing beautiful english, it may be necessary that we - the >>> community and in a continuous process - start reviewing the >>> linguistics in english. >> >> Three months ago I have asked similar question here. Precisely: what to >> do with English string that could be improved[0]? I got few other >> suggestions on how to improve that string, but nothing was done. > > That's actually the issue. Andras is helping a lot here, but he is not > the one responsible of the en_US version. And I don't think somebody is > in fact. Hmm. Sophie - should we consider spinning-up a community for en_US? I'm not sure I have much time to spend on it right now, but I could perhaps help out a little here and there... Best, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Quality in l10n
On Mon, Dec 2, 2013 at 2:37 PM, Sophie wrote: >> >> a) Can somebody layout precisely what an en_US l10n >> team/group/individual would do? > > as, I said, I think the first thing is to have an up to date glossary, > then check for the consistency in the menus/dialogs/tabs, check for the > Camel case use, check that the good terms are used for the good > functions, actions, etc and are consistent with the terms already used. > Check that the help buttons leads to help files, check that the help > files is up to date, etc. I've more but don't want to frighten you with > the tasks ;) oh, is that all? :P > So to answer Robinson and you, yes, we need somebody able to check the > en_US version. I'm ready to help in each step. > Awesome. Sophie: please point us at whatever docs/intro info you have and we can get started stubbing-in wiki pages, creating a list of TODO items, etc. Feel free to poke us every week or so if you need something more from us. Thanks, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Help pointing to TDF wiki
On Tue, Dec 3, 2013 at 3:18 PM, Olivier Hallot wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi > > Just curious: While translating conditional formatting matters, I found > at least 2 references to wiki pages with more detailed explanations. Is > this new trend for help pages? unfortunately, these pages are not > localized... links? -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Help pointing to TDF wiki
On Tue, Dec 3, 2013 at 5:09 PM, Sophie wrote: >> links? >> > I wrote this help part and sent a mail to this list on August that more > information will be on the wiki and should be translated. > https://wiki.documentfoundation.org/Faq/Calc/141 > https://wiki.documentfoundation.org/Faq/Calc/142 > https://wiki.documentfoundation.org/Faq/Calc/143 Hmm... so is the plan to link to TDF wiki pages from our docs? If we do start to link to pages under Faq* as documentation, perhaps we should establish some kind of template for those pages (e.g. "This page is now in official docs...do not move or rename this page without ") As I've mentioned previously, I think we should come up with an overarching gameplan for all of our documentation, just so that users and others who get confused easily (such as I) can keep track of it all :-) Cheers, --R * It would be nice to use /FAQ instead (looks like something is hard-coded there -- I pinged cloph about fixing it) -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Help pointing to TDF wiki
On Tue, Dec 3, 2013 at 6:52 PM, Tom Davies wrote: > Hi :) > All caps is "a bit shouty". In emails if you use all caps that is > often seen as shouting. CamelCase looks friendlier I agree that in general ALL CAPS == shouting, but I believe that applies to words spelled-out without abbreviation. In this case we're talking about a specific initialism: "Frequently Asked Questions," or FAQ. That being said, an FAQ generally refers to a short list of questions (hence the "Frequently" part...). There are currently 296 subpages of Faq/ on the wiki, so perhaps it's time for a general rename -- perhaps to 'Questions/' ? Cheers, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Help pointing to TDF wiki
On Wed, Dec 4, 2013 at 4:38 AM, Tom Davies wrote: > Hi :) > To be more correct it should really be F.A.Q. and the dots would play > even more havoc than spaces often do. Also we should always say > G.N.U./Linux rather than Linux, G.N.O.M.E. and K.D.E. > > However as acronyms become used more frequently they gradually drop > the dots and then drop the insistence of upper-case. FAQ is old and > faq or Faq is likely to become quite common. Not to plunge too far down the linguistic rabbit-hole, but I believe that initialisms only drop upper-case when they are in fact acronyms that can be easily pronounced as words. Consider: GNU is seen as 'Gnu' sometimes, GNOME is often 'Gnome', LASER is laser, but (IMHO) NSA is still NSA, KDE is rarely Kde, and FAQ is rarely Faq. Even though we could pronounce these last two "kiddy" and "fack," we pronounce them as individual letters K-D-E and F-A-Q, just as we do with F-D-O and others). But I digress...please ignore Tom and me as we go about our linguistic jousting -- unless, of course, you find it as amusing as we do... :-) --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Quality in l10n
On Thu, Dec 5, 2013 at 4:37 AM, Mateusz Zasuwik wrote: > 2013/12/2 Sophie > > And en-US team need glossary, surely. I see many inconsistent phrases like > "*Please consider restart LibreOffice* to set new features". S..what's the best way for me to identify and squash bugs in strings like this? Should I just keep an eye on core.git? Perhaps look at the compiled list of strings? Thanks, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Re: l10n process, en_US version, Help files
On Wed, Dec 11, 2013 at 11:19 AM, Sophie wrote: > Hi all, > > This mail is posted to the dev list and the l10n list, please follow up > on the l10n list. > > I would like to open a discussion on the l10n workflow, the quality of > the en_US version and the Help files. All is linked and I would like to > discuss how we can improve the process here. I'm sure that having a > better understanding between the l10n process and the dev process should > help us to improve things :) So here is a proposal, it's a bit long, > sorry for that. Hiya Sophie, I've registered for the Pootle site, and I've started to poke around on there. I'm not sure if there's anything I can do at that point in the chain -- I guess I'll have to go up one level to the help and core repos? If there's anything specific I can do re: the en_US stuff, please let me know. I've got a couple of airport layovers in my near future, so I'll have a bit of time to spend :-) > *Before updating Pootle: > - it's important for l10n team to know the approx load of work that will > be needed to achieve the whole work. Time between beta1 and rc1 is short > and that will help to better organize this time between translation and > proof reading. > - depending also on the type of changes, we could use different tools to > optimize the work. I'm not exactly sure how we import data into pootle, but perhaps we could set up some kind of web visualization tool to show the current diff (in # of strings, # of words, etc..) between what's in the upstream repos and what's in pootle. Would that be helpful? > *When the l10n start: > - we need a continuous communication and a planing of the updates made > in Pootle, those translating off line are always frightened to lose > something in the run. > - it's exhausting when you think you are over and to see a new bunch of > words coming. Knowing it in advance help to manage the time too So basically - better communication - more lead-time before strings land in pootle > *After RC1 and l10n integration > - we need to know when integration is made after our fixes, there is > currently no communication on this Perhaps documenting the process in some pages on the wiki would help i10n better-understand how this works, and lead to some simple ways to better communicate what's going on elsewhere back to the i10n teams. > *About the en_US overall quality > - the process to rely on the l10n team to fix the en_US version is ok, > even if it gives us extra work to understand what is meant before we > realized it's a mistake. So it's also error prone for all the translations. I'm still getting my feet wet here, so I'm not quite as up to speed on this process as you guys. It sounds like some of these issues are rather nuanced, such that me being fluent in English isn't necessarily going to help me track down problems much faster without some additional context, right? > - but that doesn't solve the several typos that already exist and that > are overlooked by the l10n team (e.g in the Character > Font Effect > dialog, there is Overline _c_olor and Underline _C_olor and this is the > same for several dialogs) What's our current workflow for solving those? Filing a bug, or? > - that doesn't solve also the lack of universal vocabulary used in > several dialogs (e.g Tab/Pane/Panel/Deck to name the same object or > Graphic/Picture/Image). I've nothing to propose here but to define a > glossary where developers could pick the good word but I'm not sure it > will be used Do we have a dialog with labels on all of the different parts, indicating what nomenclature we're using to refer to each dialog or component? Here's an example with a car dashboard: http://12v.org/urs/EuroUrS6InstrumentClusterDiagram.jpg Perhaps something like that would help the devs keep the naming consistent? Cheers, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] LO on Ubuntu
On Thu, Jan 16, 2014 at 4:45 PM, Michael Bauer wrote: > Right... alle Jahre wieder, as the Germans like to sing at Christmas. Ran an > Ubuntu upgrade (with the system language being Scottish Gaelic and above > English in the list of language choices in Ubuntu). Installs LO 4.1.3.2 and > suddenly I'm back to having LO in English (USA) and Gaelic has gone > completely. Hmm... > Anyone have any ideas of what went pearshaped and whether it's a LO problem > (beyond the continuing lack of a decent post-installation language selection > option) or an Ubuntu problem in case I need to file a bug? It sounds like you installed LibreOffice via an Ubuntu repo, in which case this sounds like it would be an upgrade-related bug for Canonical/Ubuntu to handle. Cheers, --R -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Amending and enhancing the help files
On Tue, Jul 1, 2014 at 5:23 AM, Sophie wrote: >> >> Also, do we have a tool that can track each modification in the english >> help file and present it for translation to our own language? > > I don't know what the wiki is able to do on that matter, thanks for > pointing it. Moggi, Kendy, any ideas? I believe the 'Translate' extension can do that: https://www.mediawiki.org/wiki/Extension:Translate https://www.mediawiki.org/wiki/File:Translate_manual_-_Translate_example_-_01._LanguageStats_long.png If there's a way to implement a review system before proposed translations go live, then perhaps the work could take place right in the wiki. I believe a few of us have suggested that we use the same extension for translation in the TDF wiki. Perhaps we could trial it there first? --R -- Robinson Tryon LibreOffice Community Outreach Herald Senior QA Bug Wrangler The Document Foundation qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Need help with translation
On Sun, Aug 17, 2014 at 2:05 PM, Lera Goncharuk wrote: > Hi all, Hi! > I translate an article in wiki TDF > (https://wiki.documentfoundation.org/ReleasePlan). There is the word «tag» in > the paragraph “Dates” of this article. Unfortunately, I don't understand its > meaning. > Quote: > “Tuesday - the tag is created on a commit that builds and passes unit-, > subsequent-, and smoke-tests; tag is announced on the devel and qa mailing > lists” > Could anybody explain me what this word mean, please? Sure -- the tag is a marker that points to a specific revision of the source code that we use to build the LibreOffice executables. Every change that we make to the source code of LibreOffice goes into a git version control repository as a "commit". When we build LibreOffice, we pick a particular commit and build the code based on that commit (and all of the commits/changes that precede it). When we create a tag for a release, we're naming a particular commit in the repository that we'll use to build the binaries for the release. Does that all make sense? Here's some more information about git and tagging: http://git-scm.com/book/en/Git-Basics-Tagging Best, --R -- Robinson Tryon QA Engineer - The Document Foundation Volunteer Coordinator - LibreOffice Community Outreach qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Need help with translation
On Sun, Aug 17, 2014 at 4:39 PM, Lera Goncharuk wrote: > Thank you. > Yes, I understand it now. Marvy :-) Thank you for your help translating the wiki! -- Robinson Tryon QA Engineer - The Document Foundation Volunteer Coordinator - LibreOffice Community Outreach qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Transfering HELP from AOO to LO
On Sat, Aug 23, 2014 at 6:33 AM, Mihovil Stanic wrote: > Hello all, > > I joined HR team few years ago, but only after LO splitted from OO. > We kept UI translation up to date, but never even tried to translate HELP > since it's massive task with over 400.000 words. > Too much for team of two people working in their free time. What can we do to recruit more people to help with translations? - Would it be helpful to have a sign at the LibreOffice booth at conferences and LinuxFests? - Have we tried recruiting students from Universities (e.g. from Linux User Groups, etc..) ? Best, --R -- Robinson Tryon QA Engineer - The Document Foundation Volunteer Coordinator - LibreOffice Community Outreach qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] Most-wanted translators?
Hi all, I just had a ping from someone in Seattle, WA regarding localization/translation. He was curious if we had a "most wanted" list for translators of particular languages. I mentioned that we have so much content that we can use just about anyone who is multi-lingual, but I was curious if there's a mention on the wiki somewhere or a way to determine which languages are most in need of new contributors. Thanks, --R -- Robinson Tryon QA Engineer - The Document Foundation Volunteer Coordinator - LibreOffice Community Outreach qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Recruiting translators/editors (was: Re: Transfering HELP from AOO to LO)
On Thu, Aug 28, 2014 at 5:35 AM, Nino Novak wrote: > On 25.08.2014 19:09, Robinson Tryon wrote: > >> What can we do to recruit more people to help with translations? > > For me (an occasional translator) the biggest hurdle is the technical > overhead needed for some of the translations. Somebody like me, who just > wants to translate a page or correct some errors - being forced to learn > pootle (or similar tools) prevents me from "just starting". I haven't really used pootle much, but it does seem a bit quirky. There are a number of things we could do to improve translations. To hop over to another piece of infra for a moment, getting the Translations extension installed on the TDF wiki will hopefully be a good step forward: https://redmine.documentfoundation.org/issues/107 > Therefore in my eyes, a simpler workflow could substantially improve > crowd-sourcing of help file translations / corrections. Example: > - present an "edit" or "translate" button on every page or even paragraph > (could / should? be restricted to registered users) Restricting edits to logged-in users is a good approach to spam/griefers, even if the content is reviewed before inclusion. > - transmit the diff of such a user-made change to a group of reviewers with > "publish" rights > - make it easy to integrate the changes back into the original page (e.g. > by buttons "accept" / "edit" / "dismiss" (if spam etc) > - make history visible (e.g. like in Wikis) so that everybody can see, who > has contributed what These all seem like they could be helpful improvements to Pootle. Some of them (e.g. making history visible) seem like they might not take a ton of development work. Does the Language team chat with the Pootle developers at all? Are they receptive to suggestions/enhancement requests? > ... well, that's just a proposal that came into my mind while reading your > question. Easy to request but heavy to implement, I suppose ;-) Some things might take more work, such as adding in a completely new review system, but others might be more straightforward. Once the Translations extension is installed in MediaWiki, it would be great if you could give some feedback about the way that it works. I believe that it integrates a number of features you mentioned including history and a mechanism for review. I'm not suggesting that MediaWiki could replace Pootle, but perhaps one tool might help to inform and improve another. Best, --R -- Robinson Tryon QA Engineer - The Document Foundation Volunteer Coordinator - LibreOffice Community Outreach qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
Re: [libreoffice-l10n] Recruiting translators/editors (was: Re: Transfering HELP from AOO to LO)
On Thu, Aug 28, 2014 at 2:10 PM, Robinson Tryon wrote: > These all seem like they could be helpful improvements to Pootle. Some > of them (e.g. making history visible) seem like they might not take a > ton of development work. Does the Language team chat with the Pootle > developers at all? Are they receptive to suggestions/enhancement > requests? > ... > ... I'm not suggesting that > MediaWiki could replace Pootle, but perhaps one tool might help to > inform and improve another. Looks like someone has had the same idea: https://github.com/translate/pootle/issues/1549 :-) Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation Volunteer Coordinator - LibreOffice Community Outreach qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
[libreoffice-l10n] LibreOffice 4.3.2 RC2 available
Dear Community, The Document Foundation is pleased to announce the second release candidate of LibreOffice 4.3.2. The upcoming 4.3.2 will be the second in a sequence of frequent bugfix release for our feature-packed 4.3 line. Please be aware that LibreOffice 4.3.2 RC2 has not been designated as ready for production use yet, however we do encourage you to try it out. A work-in-progress list of new features in LibreOffice 4.3 can be found at https://wiki.documentfoundation.org/ReleaseNotes/4.3 The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Developers and QA might also be interested in the symbol server for windows debug information (see the release notes linked below for details) Should you find bugs, please report them to the FreeDesktop Bugzilla: https://bugs.freedesktop.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/community/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs with 4.3.2 RC2 is available from our wiki: http://wiki.documentfoundation.org/Releases/4.3.2/RC2 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org -- To unsubscribe e-mail to: l10n+unsubscr...@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
