Bug 301259 - Lokalize should take one sentence as a segment for translation instead of whole string
Summary: Lokalize should take one sentence as a segment for translation instead of who...
Status: RESOLVED WORKSFORME
Alias: None
Product: lokalize
Classification: Applications
Component: editor (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Simon Depiets
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-06-06 07:38 UTC by Rajesh Ranjan
Modified: 2018-11-12 16:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rajesh Ranjan 2012-06-06 07:38:28 UTC
I am using Lokalize and I feel that the Lokalize should take one sentence as a segment/unit for translation instead of whole string. This is a major problem of all the editors based on .po format. All editors show a translator the whole string, sometimes it might be of several sentences. Here difficulty starts. It hampers:
1. Editor Usability
2. Translation Memory and its utilization
3. Translation Speed

I feel that the editor's approach to show translation unit should be changed and show the translator sentence by sentence to translate.

Reproducible: Always



Expected Results:  
one sentence should be the unit of translation instead of whole string.
Comment 1 Simon Depiets 2018-09-30 16:26:56 UTC
This might look inconvenient but it is necessary, translations platforms that split the sentences (usually using the "." character or line breaks) produce patterns that cannot be translated correctly, because the grammatical order of sentences may differ between languages, moreso within software translation when you can have '.' character pretty much anywhere in the sentence but it doesn't mean that's the end of the sentence.
Comment 2 Andrew Crouthamel 2018-10-21 05:02:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-12 16:03:56 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!