You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have generally viewed translation helps (tW, tN, tQ, and sometimes UDB) to be related to a specific ULB. That matches our paradigm for our gateway language strategy, but does not provide for the flexibility that other situations may desire. As an example, there is currently a Russian source that is not a ULB, and given our data structure and the operation of tS, the only way they could get tW, tN, or tQ resources to display in tS would be to designate the source as a ULB. A more flexible way would be to allow the creators of the helps projects to link them to one or more source projects. That would give them the option to create helps that would be linked to a non-ULB source, or even multiple sources if they so desire.
The text was updated successfully, but these errors were encountered:
We have generally viewed translation helps (tW, tN, tQ, and sometimes UDB) to be related to a specific ULB. That matches our paradigm for our gateway language strategy, but does not provide for the flexibility that other situations may desire. As an example, there is currently a Russian source that is not a ULB, and given our data structure and the operation of tS, the only way they could get tW, tN, or tQ resources to display in tS would be to designate the source as a ULB. A more flexible way would be to allow the creators of the helps projects to link them to one or more source projects. That would give them the option to create helps that would be linked to a non-ULB source, or even multiple sources if they so desire.
The text was updated successfully, but these errors were encountered: