Opened 10 years ago

Closed 10 years ago

Last modified 6 years ago

#634 closed improve feature (duplicate)

translation tool

Reported by: enriqueguillen Owned by:
Priority: major Milestone: Legacy Resolved
Component: BW Internationalization Keywords: translation tool
Cc:

Description

There is a problem concerning the translation tools. It seems that the current translation tool does not allow to translate a term when this term has two meanings and consequently two different terms in the second language that could be applied to the original language term. In order to explain this problem better this is a feedback I got from mirto:

I was translating site from en to polish. One translation of word "from" appears in two different contexts. In polish FROM (city) is different than (message) FROM (member). Translation tools put it as one word.

Where exactly it appears?

  1. on My Messages page (just under Messages recieved) - in polish it would be Od
  2. on Find members page - in search results - in member descriptions (on left side -

xx years old, FROM xxx) - in polish would be Z.

Maybe there are other places, that is what I found. Can anyone separate it on translation board as two different cases???

Code: (idword=25830) Description: This is the word 'from' English source: from

thanx,

Change History (3)

comment:1 Changed 10 years ago by micha

  • Resolution set to duplicate
  • Status changed from new to closed

see #635

comment:2 Changed 10 years ago by lemon-head

Hm, it's not exactly duplicate, as I understand it. This one is more general, and wants that we design the translation system in a way that allows for one word in language x to have two translations in language y.

I think this would be really difficult to realize with our current system. The only thing we can do as programmers is to take care that each word code is used only in one place, unless we are really sure it has exactly the same meaning and context.

This can be achieved by having wordcodes like PageAWordX, instead of just WordX.

Anyway, we can still leave this as closed.

comment:3 Changed 6 years ago by TimLoal

  • Component changed from unknown to BW Internationalization
  • Milestone changed from unassigned to Legacy Resolved
Note: See TracTickets for help on using tickets.