Issue on carriage return ... words are truncated

face

I see that (this pics is taked from viewcontroller used when add a new item) italian words are truncated ... any chance to solve that ? Don't know in other languages ...

MikeT

Hi face,



It affects all languages, we've gotten reports that it happens a lot in German.



We're trying to find a way to do this properly but the suggestions we came up with seems to have their own cons. Unfortunately, I don't know if we'll be able to find a solution for this at all but we'll keep looking for it.



For now, I'd leave it as is.

ejr

Just my opinion but design wise it looks very sloppy. At a minimum, if possible, either hyphenate correctly the words or prevent them from doing so. Another option is to abbreviate them for display not for data entry.



The main offenders ones are "membership #" and "organization".



Hope you reconsider the importance of this item.

MikeT

Hi Ejr,



If you create a new membership item, you'll see that we've already fixed that by changing to group instead of membership. You won't see it in pre-existing items because those items are saved with those field names. You'd have to erase the data and re-sync to see the newer field names in those items.



As mentioned, we have thought about many ways around it but even hyphenating/abbr. have their own cons in other languages. We'll keep looking for a solution that'll works great with everyone.



Thanks!

face

Any news about that ? in b4 the issues are still there ...

roustem

[quote name='ejr' timestamp='1354887305' post='64652']

Just my opinion but design wise it looks very sloppy. At a minimum, if possible, either hyphenate correctly the words or prevent them from doing so. Another option is to abbreviate them for display not for data entry.

[/quote]



It is not a trivial task. There is no support for hyphenation in iOS and implementing our own would take a lot of effort considering all localization requirements.



There only options available are: wrapping by character, wrapping by word, or truncation.

face

wrapping by word it would be perfect or i'm missing something ???

khad

[quote]wrapping by word it would be perfect[/quote]

I agree. That would seem like a good solution and not the one that is currently implemented according to ejr's screenshots above. I'll file this and see what can be done. Perhaps I also am missing something. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />

face

4.1 b10 the issue is still there

ejr

Wrapping is ok as long as it is done correctly and by that I mean that wrapping one character is not enough.

For example



organiza

tion



is ok graphically

-----

organizatio

n



is not

-----

roustem

When the word is long there is no way to wrap it correctly by a character.



I do understand your point of "oraniza-tion" vs "organizatio-n". There are no built-in rules for that in iOS. The only way for us to do this would be to spend several months to re-implement the labels and define hyphenation rules for every language. It is a very hard problem.



Instead of wrapping by character we can enable by wrapping words. It will help when the words are short but it makes no sense for some values, for example, for generated passwords.

ejr

Agreed on the difficulty.



As a minimum you could make a rule so that no matter the language, never have one letter orphaned. Use 2 letters or 4 based on word length. It will not be correct but "graphically" it will look better.



Or just substitute ellipsis for the last 4 letters with a Pop over/slidder for the cases that the word cannot be figured out in context.



organizati…

organizaci…

membersh…

membresí…

face

[quote name='roustem' timestamp='1357155910' post='66694']

Instead of wrapping by character we can enable by wrapping words.

[/quote]



And you'll do it in the next beta ??

I think this is the best solution, after that we translator could arrange the residual words too long to fit the little space trying to change long words into similar shorter one ...

MikeT

No, we haven't decided yet on how to fix it yet. We're working on a different way to fix this but I don't have a timeframe on when yet. Once we have a solution, we'll announce it in this forum.