-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
Text segmentation and text segmentation search in instant-translate only will be done only when for the current search TM is available or risk-predictor (ModelFront) is enabled.
-
Emptyshow more show less
Problem
Currently the only validation if the searched text is valid for segmentation is when the segment contains more then 1 sentence.
Example of possible search test and the number of sentences:
| nr of segments = 0 | nr of segments = 1 | nr of segment > 1 |
|---|---|---|
| ' ' | This house is blue. | One house is blue. One is red. |
| . | A house?? | Red? Yes! |
| A house? | ||
| A house ? | Red: one | |
| A house! ! |
The problem occurs when for the current request there are only MT resources configured. And since all MT resources have static match-rate (no risk-prediction available ex: ModelFront), always the first queried resource will be displayed as result. Instant-translate segmentation should be active only when for the current search request there is TM configured and available or when machine translation risk-predictor is enabled (ex: ModelFront)
[TRANSLATE-2278] Check if the searched text is valid for segmentation
| Status | Original: Final pull request made [ 10005 ] | New: Done [ 10000 ] |
| Rank | New: Ranked lower |
| Workflow | Original: MittagQI Workflow [ 30159 ] | New: MittagQI Workflow with Peer [ 36460 ] |
| ChangeLog Description | Original: Text segmentation and text segmentation search in instant-translate only will be done only when fro the current search TM is available or risk-predictor (ModelFront) is enabled. | New: Text segmentation and text segmentation search in instant-translate only will be done only when for the current search TM is available or risk-predictor (ModelFront) is enabled. |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Test Ready [ 10005 ] |
| Description |
Original:
h3. Problem Currently the only validation if the searched text is valid for segmentation is when the segment contains more then 1 sentence. Example of possible search test and the number of sentences: ||nr of segments = 0||nr of segments = 1||nr of segment > 1|| |' '|This house is blue.|One house is blue. One is red.| |.|A house??|Red? Yes!| | |A house?!|Red? Yes!!| | |A house ?|Red: one| | |A house! !| | The problem occurs when for the current request there are only MT resources configured. And since all MT resources have static match-rate (no risk-prediction available ex: ModelFront), always the first queried resource will be displayed as result. Instant-translate segmentation should be active only when for the current search request there is TM configured and available or when machine translation risk-predictor is enabled (ex: ModelFront) |
New:
h3. Problem Currently the only validation if the searched text is valid for segmentation is when the segment contains more then 1 sentence. Example of possible search test and the number of sentences: ||nr of segments = 0||nr of segments = 1||nr of segment > 1|| |' '|This house is blue.|One house is blue. One is red.| |.|A house??|Red? Yes!| | |A house?| | |A house ?|Red: one| | |A house! !| | The problem occurs when for the current request there are only MT resources configured. And since all MT resources have static match-rate (no risk-prediction available ex: ModelFront), always the first queried resource will be displayed as result. Instant-translate segmentation should be active only when for the current search request there is TM configured and available or when machine translation risk-predictor is enabled (ex: ModelFront) |
| Fix Version/s | New: translate5 - 5.0.12 [ 11502 ] |
| Status | Original: Selected for Development [ 10100 ] | New: In Progress [ 3 ] |
| Status | Original: Open [ 10002 ] | New: Selected for Development [ 10100 ] |
| ChangeLog Description | New: Text segmentation and text segmentation search in instant-translate only will be done only when fro the current search TM is available or risk-predictor (ModelFront) is enabled. |