Search by property

Jump to: navigation, search

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Has summary" with value "Different words have different translations, depending on context.". Since there have been only a few results, also nearby values are displayed.

Showing below up to 13 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


List of results

    • Aisle/Features/Latin Script  + (Editing Latin script shouldn't be a challenge, but what would we do without it.)
    • Aisle/Paradigms/Federation  + (Federation is important if you're in a glo
      Federation is important if you're in a global and distributed ecosystem. There are many reasons why you'd want to use a different tool, or why you'd like an online tool hosted independently. Being able to exchange work between multiple tools and their installs is important.
      ple tools and their installs is important.)
    • Aisle/Paradigms/Interoperability  + (Interoperability means that using one tool doesn't lock you in to that tool, let alone a particular installation of that tool.)
    • Aisle/Features/Language packs  + (Language packs are great ways to create testable deliverables, with minor install hurdles.)
    • Aisle/Use Cases/New contributor  + (New contributors need a bit of help to get by, and should see reward for their work quickly. Low barrier of entry matter as well as opportunities for experienced contributors or mentors to guide. This has Grow Mozilla impact, of course.)
    • Aisle/Paradigms/Discoverability  + (One of the biggest hurdle in taking contri
      One of the biggest hurdle in taking contributions to an open source project is finding them. If you have a central install of a tool, say, github, or a particular narro install, owners can use the features there. But in a truly distributed fashion, it's a tough challenge to discover possible contributions, and mentor new contributors to team members or leads.
      new contributors to team members or leads.)
    • Aisle/Requirements/Performance  + (Perceived performance in a localization tool is to be kept in mind on features.)
    • Aisle/Features/Spellchecking  + (Spellcheckers should run over the localized string values.)
    • Aisle/Use Cases/Sprint  + (Sprints are a powerful tool to make signif
      Sprints are a powerful tool to make significant progress in a localization project, enjoying the high bandwidth communication of a group of people being together focused on one task. Usually sprints are held in real-life, though virtual sprints are also happening. You'd want an experienced contributor to guide the sprint, and pair that with possiby quite new contributors.
      that with possiby quite new contributors.)
    • Aisle/Paradigms/Attribution  + (The biggest value that FLOSS projects can
      The biggest value that FLOSS projects can give back to their contributors is Attribution. Just tell the world who did what. In particular with the rise of distributed version control systems, having attribution as part of the version control history is key. Also, MPL 2 builds on that, and removed attribution from the license header. Thus, a good l10n tool for an open source project should create open source l10n code, with changesets that give attribution to the contributors, no matter where they originally made their contribution. It should be noted that DVCSes only know about Authors, and possible Committers. Roles like Reviewer or Proofreader are probably best stored in the commit messages.
      obably best stored in the commit messages.)
    • Aisle/Goals/Correctness  + (The correctness of a translation is per entity linguistic correctness.)
    • Aisle/Features/Collaborative Editing  + (Think Etherpad. Collaborative Editing allows multiple contributors to edit the same file at the same time, seeing the mutual edits live.)