Sharetribe/Sharetribe Go

Want to see Sharetribe Go in your language? Join the translation team and help with the translations!

Obsolete 🔒 💬 Discussions ⚙
conversations.confirm.cancel_description

If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.

History

If your request was not fulfilled, you can mark it as 'not happened'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'not happened'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'not happened'. You can still give feedback to the other party and describe what happened.

No previous version to compare to.

changed by Antti Virolainen 01 April, 2013 20:40.
If your request was not fulfilled, you can mark it as 'not happened'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'not happened'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'not happened'. You can still give feedback to the other party and describe what happened.

No textual difference compared to previous version.

changed by Antti Virolainen 05 February, 2014 08:54 via a Batch Operation.
If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
- ~~If your request was not fulfilled, you can mark it as 'not happened'. You can still give feedback to the other party and describe what happened.~~
- If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
changed via the API 02 July, 2015 14:03.
No previous version to compare to.

changed via the API 02 July, 2015 14:03.
If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.

No textual difference compared to previous version.

changed by Thomas Malbaux 03 December, 2015 13:10 via a Batch Operation.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
- ~~If your request was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.~~
- If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
changed via the API 21 January, 2016 09:01.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.

No textual difference compared to previous version.

changed by Thomas Malbaux 29 February, 2016 11:11 via a Batch Operation.
If your order was not fulfilled, you can mark it as 'canceled'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'canceled'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'canceled'. You can still give feedback to the other party and describe what happened.
- ~~If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.~~
- If your order was not fulfilled, you can mark it as 'canceled'. You can still give feedback to the other party and describe what happened.
changed by Sharetribe Team 28 October, 2019 07:00 via a Batch Operation.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
- ~~If your order was not fulfilled, you can mark it as 'canceled'. You can still give feedback to the other party and describe what happened.~~
- If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
changed by Sharetribe Team 11 December, 2019 10:25 via a Batch Operation.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.
If your order was not fulfilled, you can mark it as 'disputed'. You can still give feedback to the other party and describe what happened.

No textual difference compared to previous version.

changed by Sharetribe Team 30 January, 2020 08:06 via a Batch Operation.

About Segments

A segment (or string in developer’s parlance) is a piece of text extracted from a linguistic file. It has many translations.

Segment Statuses

In WebTranslateIt segments have statuses. The status is represented by a color indicator to its right.

Plain Green	Proofread (segments translated and reviewed)
Dotted Orange	Not Proofread (segments translated but not reviewed)
Dotted Red	Not Translated
Double Yellow	To Verify (segments translated, but then the source text was changed after that. Or, segment translated by machine translation)
Solid Grey	Hidden (segments hidden by a manager)
Dotted Grey	Obsolete (Segments not found in the master file during last sync)

More about segments in the documentation.

Proofread (Completed) Segment

A proofread segment has had its translation read by a proofreader and any errors have been marked or corrected.

Who can and how to proofread?

Managers and translators with proofreading rights can proofread a segment by ticking the segment’s checkbox located at the top right corner of a segment. Proofread segments appear with a green indicator.

How to unproofread a segment?

Managers and translators with proofreading rights can unproofread a segment by un-ticking the segment checkbox. Editing and changing the translation of a proofread segment also marks the segment as unproofread.

More about segments in the documentation.

Unproofread Segment

An unproofread segment is a segment that has not been read and validated by a proofreader. Unproofread segments appear with a orange, dotted indicator.

How to proofread a segment?

Managers and translators with proofreading rights can proofread a segment by ticking the segment checkbox.

More about segments in the documentation.

Untranslated Segment

An untranslated segment is a segment that has not been translated nor proofread yet. An untranslated segment can be proofread in which case its status is proofread. This is useful when a segment must be intentionally be left blank for instance. Untranslated segments appear with a red, dotted indicator.

How to translate a segment?

Managers and translators can translate a segment by clicking on the translation area.

Managers and translators can then type their translation in the translation area and click on the green Save button to save the translation.

The translation is now saved and has the “unproofread” status.

More about segments in the documentation.

To Verify Segment

A segment to verify is a segment for which the translation needs to be verified by a translator or proofread for one of the following reasons:

The segment was translated but the source text (therefore the meaning of the segment) was changed afterwards.
Or a manager found a translation they thought should be looked at and manually marked a translation as to verify.

In both cases a translator will need to check if the translation is still correct with the new source text, will make amendments if necessary and mark the segment as unproofread.

Segments to verify appear with a orange, double-lined indicator.

How to remove this “to verify” status?

Managers and translators can mark the segment back to “unproofread” by editing the segment or clicking on the checkbox.

More about segments in the documentation.

Obsolete Segment

An obsolete segment is a segment that is no longer in use in your project. Instead of deleting this segment and its translations, we put it in a temporary category, “obsolete”, so that you can recover it and its translations. Obsolete segments are hidden from translators.

Why are my segments marked as obsolete?

Segments don’t become obsolete by themselves. When someone uploads a new version of your file in which a segment was removed it will then be removed from WebTranslateIt as well. We call that obsoleting a segment. For more information and concrete examples check our documentation on obsoleting segments.

How can I un-obsolete a segment?

You can mark a segment as active by uploading a version of your file that contains that segment, or by marking the obsolete segment as active.

More about segments in the documentation.

Hidden Segment

A hidden segment is a segment that was hidden by a manager. Hidden segments are not visible by translators. Only managers can hide segments by clicking on the options button » Hide segment.

Managers can mark a hidden segment back to active by clicking on the options button » Flag segment as active.

More about segments in the documentation.

Plural Segments

A plural segment is a segment which often includes a countable variable placeholder (a number for which the value can vary programmatically). Nouns are inflected by this grammatical number and generally have different forms for singular and plural. In English for instance we decline the word dog in 1 dog and 2 dogs.

You can use the help tools given in the translation interface to translate these segments.

Important You may have more or less plural forms in your target language than in your master language. Plurals are different in many languages. For more information read the section about plural segments in the FAQ and in the documentation.

AutoSave

AutoSave is a feature that you can activate and deactivate in the toolbar. When turned on saving translations on the translation interface happens automatically without clicking on the “Save” button, which is not present.

More about AutoSave in the documentation.

Master

Master usually means source, as opposed to target.

It can refer to the master language, the source language on your project. There can only be one master language per project.

It can also refer to the master file, a language file in the master language.

A Target Language is the language you translate your project to. There can be one or many target languages per project.

More about languages and files in the documentation.

Target

Target usually refers to the languages you translate your project into, as opposed to the source or master language.

A target language is a language you translate your project into. There can be several target languages in a project.

A Target File is a file containing all the translations made into one language. A Target File is a copy of the Master File but in the target language.

More about languages and files in the documentation.

Advanced Search

WebTranslateIt’s search engine lets you search for segments and translations. Many options let you refine your search.

Where to search: all, key, source, target

Right next to the search box you will find 4 options to refine your search.

All searches for some text into the segment’s key names, in the source text and in the target text. You will get a lot of results but this is generally a good option to quickly search for something.
Key lets you target specifically the segment’s key. The search engine won’t look at all in the translation’s text.
Source lets you specifically query for the source text. It will look for a stand-alone word in the source text.
Target lets you specifically query for the target text. It will look for a stand-alone word in the target text.

Regex Search

Regex search lets you search for anything using a POSIX regular expression.

Ignore Case

Ignore case lets you choose whether your search is case sensitive or not. Searching for Air with case sensitivy on won’t match words such as repair or commanditaire but will match sentences containing as Air Drop or Air quality. With “Ignore Case” turned on it will match all of these segments.

Collaborators

Collaborators are users working on at least one project of your organization.

You can’t manually add new collaborators to an organization. Collaborators are added automatically when you invite someone to a project or Team.

On the other hand, removing a collaborator from your organization revokes their access to all of your Projects and Teams. It’s a great way to remove an ex-employee from all your projects, teams and organization.

Clicking on the ⋆ icon flags a collaborator as an Admin. It means that this collaborator will be able to create new projects for your organization and assign projects to Teams.

More about Roles and Collaborators in the documentation.

Sharetribe/Sharetribe Go

History

Keyboard Shortcuts

Navigation

On highlighted segment

On open segment

Glossary

About Segments

Segment Statuses

Proofread (Completed) Segment

Who can and how to proofread?

How to unproofread a segment?

Unproofread Segment

How to proofread a segment?

Untranslated Segment

How to translate a segment?

To Verify Segment

How to remove this “to verify” status?

Obsolete Segment

Why are my segments marked as obsolete?

How can I un-obsolete a segment?

Hidden Segment

Plural Segments

AutoSave

Master

Target

Advanced Search

Where to search: all, key, source, target

Regex Search

Ignore Case

Collaborators