We can see all the translated items using Settings > Application Terms > Translated Terms.
But there is no dynamic translated values in the list. All are static values like labels. However, I made some queries in PostgreSQL and I found some translated values there.
Is there any UI to check and edit the translated field values in Odoo 10?
Usually the field itself has a little globe on the right upper corner in edit mode. For example in products:
Click to open the field's translations:
Another, and in my opinion better, way is using the module web_translate_dialog from OCA.
And that's it. You already found the menu with the list of records from model ir.translation which show every translation for the system. The little globe is opening it, too, but filters the correct field.
Related
Is there a way to make the language property list shorter? Make it show only EN-US and PT-BR, for instance, so it's easier to find them?
You probably don't need to do it.. You can likely just make your life easier like:
Make a new form, lets say it's called LocalForm.vb
Drop a label on it, lets say called HelloLabel
Set form to de-DE, set the text of the label to Hallo
Set form to fr-FR, set the text of the label to Salut
Set the form back to (default) - you now have LocalForm.resx, LocalForm.de-DE.resx and LocalForm.fr-FR.resx and you can add controls
Add a Button, called StartButton
Double click the LocalForm.de-DE.resx file
Dismiss the "if you mess this up you'll have to fix it yourself" dialog
Add a line for StartButton.Text Starten
Repeat for other language files
Dropping a control named XyzButton on the form, and then visiting each LocalFor.*.resx in turn and adding the locale for it is a lot easier than back-and-forthing with the language setting, though I know why it's done the way MS chose to do it - you're supposed to lay your form out perfectly with all its hundreds of controls, and then switch to French and write all the French for all hundreds controls, and then switch to German and write it all in German.. In a use case like that there isn't a lot of work to do with that awkwardly huge Language dropdown. Incremental adds that way are a bit of a pain..
Perhaps raise a connect bug/feature asking them to put the "already used" languages (as determined by the presence of Form.*.resx files) at the top of the list, and wait many years for it to be implemented :)
Note: There's a bit of a nuisance with this "edit the resx" in that if you rename a control it doesn't always get picked up. Last time I was localizing I threw together an app that watched (FileSystemWatcher) files named *Form.resx and if it saw a change (load the current version, compare to the prev version) that was a rename, it made the same change in the other files (or maybe alerted if they weren't in sync.. can't quite remember now and I've no idea where the code has gone)
Maybe don't rename your controls after you first decide a sensible name for them/add them to the translated resx..
I use the search in JIRA about 50 times a day and every time it forgets what I just entered. Is there any way to tell it to remember the last search or the project code. (By project code I mean the first few letters of bug code such as "AAQT-").
That prefix is known as the project key.
(Also, what version of JIRA are you using? There are some UI differences between Cloud and most Server instances so my following advice might not make sense.)
There isn't a way to pre-define the project key in the quick search box since most JIRA instances have multiple projects, and pre-defining it for just one project doesn't make sense.
However, your browser should be able to remember previous values entered. You would have to overwrite the numerical portion that follows the key, though.
Do you mean save your search as your favourite filter? If so then you can follow these steps :
Click on "Issues" dropdown then choose "Search for issues"
Click on "New filter" button on the top-left area
Type your query
Click on "Save as" button on the above of query field
Give any search name, then it will be save under "Favourite Filters" section
Please how can i change text and links in the highlited zones in the picture below :
Click to see
Thanx a lot
Prestashop comes with a translation mechanism. Usually from your Prestashop backend, navigate to Localization > Translation, then identify "Modify Translations ". Select the type of translation, the theme and the language and hit on the button "Modify" on the right hand side. Look for any module in the front office translations group that contains "search".
Your situation may be a little be different because you are not using the default theme. You theme developer has probably created a new quick search module. You would need to identify the actual module and it should be easy to identify it from the list of translatable module. If the module is not well developed, it will not be possible to modify them. In that case, you should ask your theme developer.
I hope it help. Good luck with your business.
I am working on af:query for Search functionality in ADF. The code for same is given below
<af:query id="qu1" headerText="Search" disclosed="true" styleClass="quButton" saveButtonText="Save"
value="#{bindings.SearchByTitleAndAuthor.quDescriptor}"
model="#{bindings.SearchByTitleAndAuthor.quModel}"
queryListener="#{bindings.SearchByTitleAndAuthor.processQuery}"
queryOperationListener="#{bindings.SearchByTitleAndAuthor.processQueryOperation}"/>
This provides me a Search region with various fields and 2 radio buttons named as "All" and "Any".
My requirement is that the word "Match" should come before the radio button "All". I have checked on different links that the word "Match" comes by default when we use af:query. But, its not coming in my case. Please suggest some ways in which I can get it done.
My Jdeveloper version is "Studio Edition Version 11.1.1.7.0".
Check your view object. Ensure that show match all/match any is checked as shown in the screenshot.
===EDIT===
OP was using custom skin. Causing the issue. After removing the custom skin, the issue went away as suggested.
For each model element, there is the option in EA 10 to create internal requirements, constraints and scenarios. All of them end up in reports if you use the pre-defined Basic Template.
However, if you select "structured specification" instead of the default "description" text field for a scenario, then I end up with the steps of the structured specification being ignored in the report output.
How can I have them included in reports?
It sounds like you need to create your own reporting template. This may seem a bit daunting first time out and the template editor is pretty ornery, but luckily you can use an existing template as a starting point.
Hit F8 to bring up the Generate Documentation dialog, then select the Templates tab. Click New, specify a name and select a template you like to be copied. Don't bother with a template group, and leave the fragment checkbox unchecked.
In the editor, scroll down about halfway (assuming you selected to copy the Basic template) and locate the yellow scenario > tag.
Now in the checkbox tree on the left, scroll down do Package - Element - Scenario. Note that Scenario is checked, but Structured Scenarios is not. Check it.
In the editor, note the new structured scenarios > tag. Remove the right-click-to-insert text, then right-click and select Insert Field, then State etc.
It's more than a little fiddly, but if the Basic template is good enough to begin with you should be able to add the structured scenarios with a minimum of effort.
For more information, see the help file under Reporting - RTF Documents. Note that the individual fields aren't listed in the help file, you need to open up the template editor to see what specific information you can extract to your report.