Description: https://help.libreoffice.org/latest/ru/text/scalc/guide/format_value_userdef.html Steps to Reproduce: EN: 1. Follow the link above in the ‘description’ 2. We reach step 3 and then we find a problem. RU: 1. Действуем по ссылке выше в ‘description’ 2. Доходим до 3 шага и тут обнаруживаем проблему. Actual Results: EN: The inability to use a custom format RU: Отсутствие возможности применять собственный формат Expected Results: EN: According to the instructions, it is possible to use your own format RU: Согласно инструкции возможно применять собственный формат Reproducible: Always User Profile Reset: Yes Additional Info: EN: The RUS language pack is installed RU: Установлен языковой пакет RUS
This is a documentation (actually, localization) problem. The English help tells to choose "User-Defined", which is there. In Russian UI, that is "Особый", not "Пользовательский". But the idea behind the whole #3 in help is unclear. Why would one need to choose that item? One can go straight to #4? and enter an own custom format to the "Format Code" box - that would switch to the custom format automatically. I don't know if this should be moved or not. My gut feeling is that this is better asked at forumooo.ru, where the person doing the Russian localization can read it.
(In reply to Mike Kaganski from comment #1) > This is a documentation (actually, localization) problem. The English help > tells to choose "User-Defined", which is there. In Russian UI, that is > "Особый", not "Пользовательский". > > But the idea behind the whole #3 in help is unclear. Why would one need to > choose that item? One can go straight to #4? and enter an own custom format > to the "Format Code" box - that would switch to the custom format > automatically. > > I don't know if this should be moved or not. My gut feeling is that this is > better asked at forumooo.ru, where the person doing the Russian localization > can read it. Is it possible to save this number 0373100115223000016 as text when copying? At 2 values or more, when inserted, these immediately turn into something else. Возможно ли данное число 0373100115223000016 сохранить как текст при копировании? На 2 значениях и больше при вставке подобные сразу превращаются в нечто иное.
(In reply to Roman from comment #2) 1. You are not discussing the issue that you created - you are asking "how to use the program" question. This is off-topic on this Bugzilla site. Use ask.libreoffice.org (English), or already mentioned Russian forum, for this kind of questions. 2. Answering this off-topic question - yes, it is possible either by pre-formatting cells (columns) as text, or by prepending the text by an apostrophe.
(In reply to Mike Kaganski from comment #3) > (In reply to Roman from comment #2) > 1. You are not discussing the issue that you created - you are asking "how > to use the program" question. This is off-topic on this Bugzilla site. Use > ask.libreoffice.org (English), or already mentioned Russian forum, for this > kind of questions. > > 2. Answering this off-topic question - yes, it is possible either by > pre-formatting cells (columns) as text, or by prepending the text by an > apostrophe. 1. Yes. Indeed, machine translation is wildly unclear. I found everything and it works. Is it possible to expand the page for understanding? 2. I have identified a problem at the level of conditional formatting, do I need a new appeal?
(In reply to Roman from comment #4) > Is it possible to expand the page for understanding? What "expansion" do you mean? The problem discussed here is (a) wrong Rossian translation of the help, and (b) unnecessary step #3, which is best simply removed from there. > 2. I have identified a problem at the level of conditional formatting, do I > need a new appeal? If you have a different issue, please file a different bug. One issue per one bug please.
(In reply to Mike Kaganski from comment #5) > (In reply to Roman from comment #4) > > Is it possible to expand the page for understanding? > > What "expansion" do you mean? The problem discussed here is (a) wrong > Rossian translation of the help, and (b) unnecessary step #3, which is best > simply removed from there. It is valid to delete step 3. And the application is completed
Actually, step 3 allows user to check if the desired custom format has not been entered already. It could be "burried" in the many existing "Number" formats. My suggestion is to add "(optional)" to the step 3 text in the Help page.
(In reply to Olivier Hallot from comment #7) > Actually, step 3 allows user to check if the desired custom format has not > been entered already. 1. This is not stated there in the help. 2. This step is not needed at all to perform the final goal of that help page: which is *defining* own formats, not "finding already present" custom formats. 3. As I said, the very first keypress in the step #4 will bring you to the User-Defined category anyway. We can all invent additional steps potentially useful in this or that situation. Being *minimal* without additional stuff helps users. > My suggestion is to add "(optional)" to the step 3 text in the Help page. If wanted, please keep it not in the sequence, but - as any additional stuff - somewhere below, in some notes / tips / whatever.
(In reply to Mike Kaganski from comment #8) > Being *minimal* without additional stuff helps users. Let me clarify myself: I don't mean, that the whole help page must be minimal. Not at all; I welcome help pages incorporating as much related information as possible. What needs to be minimal is the sequence to perform the task, presented in the 1-2-3 steps. Anything else must be in separate paragraphs, as discussion / technical reference, or the likes, outside of the sequence.
(In reply to Mike Kaganski from comment #1) > This is a documentation (actually, localization) problem. The English help > tells to choose "User-Defined", which is there. In Russian UI, that is > "Особый", not "Пользовательский". I've suggested it: https://translations.documentfoundation.org/translate/libo_help-master/textscalcguide/ru/?checksum=987da1d3cfa90e9a#suggestions Marking as "new" for improvement suggested in comment 8.
(In reply to Stéphane Guillou (stragu) from comment #10) > I've suggested it: Your suggestion is correct (I can't approve it myself).