16 branding defects fixed.

This commit is contained in:
axiom
2025-01-29 16:44:37 +03:00
committed by Nikita Iarychenko
parent be1af3585d
commit a2251eac38
23 changed files with 92 additions and 92 deletions

View File

@@ -317,7 +317,7 @@ artifacts.menu.item.rebuild=Rebuild
artifacts.menu.item.edit=Edit\u2026
error.task.0.execution.failed=Task {0} failed, please see idea.log for details
dialog.title.choose.module=Choose Module
build.process.no.javac.found=No system java compiler is provided by the JRE. Make sure tools.jar is present in IntelliJ IDEA classpath.
build.process.no.javac.found=No system java compiler is provided by the JRE. Make sure tools.jar is present in IDE classpath.
build.process.no.javac.path.found=Cannot determine path to ''tools.jar'' library for {0} ({1})
build.process.no.free.debug.port=Cannot find free port to debug build process
build.process.ecj.path.does.not.exist=Path to eclipse ecj compiler does not exist: {0}

View File

@@ -406,7 +406,7 @@ add.external.annotations.path.description=Select path in which external annotati
sdk.configure.sourcepath.tab=Sourcepath
error.message.please.enter.valid.library.files.path=Please enter valid library files path
add.new.module.text.full=Module
project.roots.classpath.format.default.descr=IntelliJ IDEA (.iml)
project.roots.classpath.format.default.descr=IDE (.iml)
module.classpath.button.edit=Ed&it\u2026
choose.modules.dialog.description=Library ''{0}'' will be added to the selected modules.
dialog.message.no.suitable.modules.for.0.facet.found=No suitable modules for {0} facet found.
@@ -574,7 +574,7 @@ notification.content.no.files.were.downloaded.multiple=No files have been downlo
library.jars.diff.dialog.0.jars.differ.from.1.library.jars={0} JARs differ from the ''{1}'' library JARs.
library.jars.change.coordinates.action.title=Change Coordinates\u2026
project.structure.dialog.title.choose.libraries=Choose Libraries
add.idea.module.label=Add Intellij IDEA module
add.idea.module.label=Add IDE module
existing.sources=Existing sources
label.ipr.file.based=.ipr (file-based)
label.directory.based={0} (directory-based)
@@ -602,7 +602,7 @@ checkbox.move.classes.to.separate.source.root=Move classes to a separate source
dialog.title.specify.path.to.new.source.root=Specify Path to New Source Root
dialog.message.failed.to.extract.module=Failed to extract a module: {0}
select=Select
intellij.idea.module.file.iml=Intellij IDEA module file (*.iml)
intellij.idea.module.file.iml=IDE module file (*.iml)
directory.with.existing.sources=directory with <b>existing sources</b>
label.existing.library.will.be.used=<b>{0}</b> library will be used
progress.text.searching.for.libraries=Searching for libraries. Please wait.

View File

@@ -11,8 +11,8 @@ java.missed.sdk.wait.installation=Please wait while the IDE installs JDK
java.onboarding.module.name=Onboarding tour
java.onboarding.module.description=A brief overview of the main features in {0}.
java.onboarding.lesson.name=Get Acquainted with IDEA
java.onboarding.change.ui.settings=For this lesson, IDEA changes some UI settings to the default state. \
java.onboarding.lesson.name=Get Acquainted with OpenIDE
java.onboarding.change.ui.settings=For this lesson, IDE changes some UI settings to the default state. \
Your preferences will be restored when you complete or exit the lesson.
java.onboarding.project.view.description=The <strong>Project view</strong> is one of the main tool windows. It contains the project directory, SDK-specific external libraries, and scratch files. Click the striped button to preview the demo project content. You can also open it by pressing {0}.
java.onboarding.balloon.project.view=Click to open the <strong>Project view</strong>
@@ -46,7 +46,7 @@ java.onboarding.choose.values.item=Now you can start typing {0} to reduce the co
java.onboarding.invoke.completion.tip=<strong>Tip</strong>: <ide/> shows completion options automatically as you type. \
Also, you can press {0} to show completion items in any place of the code.
java.onboarding.invoke.intention.for.warning.1=You have just fixed a bug, but you can make this code look even better. \
IDEA highlights and adds a yellow bulb to the code lines that can be improved.
IDE highlights and adds a yellow bulb to the code lines that can be improved.
java.onboarding.invoke.intention.for.warning.2=Press {0} to preview the warnings and apply a quick-fix.
java.onboarding.invoke.intention.for.warning.balloon=Press {0} to show available quick-fixes
java.onboarding.select.fix=Apply the first item: {0}. In this case, the <strong>for-each</strong> loop will make code easier to understand.

View File

@@ -23,7 +23,7 @@ import javax.swing.JList
const val javaLanguageId: String = "JAVA"
internal class JavaLangSupport : JavaBasedLangSupport() {
override val contentRootDirectoryName: String = "IdeaLearningProject"
override val contentRootDirectoryName: String = "JavaLearningProject"
override val projectResourcePath: String = "learnProjects/java/LearnProject"
override val primaryLanguage: String = javaLanguageId

View File

@@ -103,7 +103,7 @@ internal fun LessonContext.contextActionsForJavaOnboarding(sample: LessonSample)
class JavaOnboardingTourLesson : OnboardingTourLessonBase(ideaOnboardingLessonId) {
override val demoFileExtension: String = "java"
override val learningProjectName: String = "IdeaLearningProject"
override val learningProjectName: String = "JavaLearningProject"
override val sample = javaOnboardingTourSample
override val completionStepExpectedCompletion: String = "length"

View File

@@ -1291,8 +1291,8 @@ inlay.parameters.java.new.expr=Calls to parametrized constructors.
# suppress inspection "UnusedProperty"
inlay.parameters.java.clear.expression.type=Method calls that use a complex expression as an argument, for example, the ternary operator or a Java 13 switch statement.
inlay.MethodChainsInlayProvider.description=Method return types in call chains.
inlay.annotation.hints.inferred.annotations=Annotations that IntelliJ IDEA generates by scanning libraries and project code. These annotations help you understand code contracts and improve the capabilities of static analysis. They include: <br> @Contract <br> @Nullable <br> @NotNull <br> @Unmodifiable <br>@UnmodifiableView <br><br><a href='https://www.jetbrains.com/help/idea/inferring-nullity.html#inferred-annotations'>Documentation</a>
inlay.annotation.hints.external.annotations=Annotations that are stored outside your source code.<br>These annotations are useful when you need an annotation, but adding it to the source code is not an option (for example, when working with a library code).<br><br><a href='https://www.jetbrains.com/help/idea/external-annotations.html'>Documentation</a>
inlay.annotation.hints.inferred.annotations=Annotations that IDE generates by scanning libraries and project code. These annotations help you understand code contracts and improve the capabilities of static analysis. They include: <br> @Contract <br> @Nullable <br> @NotNull <br> @Unmodifiable <br>@UnmodifiableView <br><br><a href='https://www.jetbrains.com/help/idea/inferring-nullity.html#inferred-annotations'>Documentation (TODO: change link to OpenIDE)</a>
inlay.annotation.hints.external.annotations=Annotations that are stored outside your source code.<br>These annotations are useful when you need an annotation, but adding it to the source code is not an option (for example, when working with a library code).<br><br><a href='https://www.jetbrains.com/help/idea/external-annotations.html'>Documentation (TODO: change link to OpenIDE)</a>
show.import.popup.for.classes=&Classes
show.import.popup.for.static.methods.and.fields=&Static methods and fields
exclude.import.wildcard.comment=Use the * wildcard to exclude all members of a specified class or package
@@ -1331,7 +1331,7 @@ title.package.not.found=Package Not Found
title.packages=Packages
title.packages.to.use.import.with=Packages to Use Import with '*':
to.import.a.method.statically.press.0=To import a method statically, press {0}
unscramble.detect.analyze.threaddump.from.clipboard.item=Automatically detect and analyze thread dumps copied to the clipboard outside of IntelliJ IDEA
unscramble.detect.analyze.threaddump.from.clipboard.item=Automatically detect and analyze thread dumps copied to the clipboard outside of IDE
unscramble.log.path.label=&Log file:
unscramble.no.unscrambler.item=<No unscrambler installed>
unscramble.normalize.button=&Normalize
@@ -1719,7 +1719,7 @@ dfa.constraint.not.null=not-null
dfa.constraint.0.not.null={0} (not-null)
dfa.constraint.null.or.0=null or {0}
label.class.pattern.syntax.explanation=Leave the method blank to represent constructors\nAny * will match against one or more characters in the qualified name (including dots)
dialog.message.modules.dont.refer.to.existing.annotations.library={0, choice, 0#Module|2#Modules} {1} {0, choice, 0#doesn''t|2#don''t} refer to the existing ''{2}'' library with IntelliJ IDEA nullity annotations. Would you like to add the {0, choice, 0#dependency|2#dependencies} now?
dialog.message.modules.dont.refer.to.existing.annotations.library={0, choice, 0#Module|2#Modules} {1} {0, choice, 0#doesn''t|2#don''t} refer to the existing ''{2}'' library with IDE nullity annotations. Would you like to add the {0, choice, 0#dependency|2#dependencies} now?
tab.title.slices.grouped.by.nullness=\ (Grouped by Nullness)
exclude.0.from.auto.import=Exclude ''{0}'' from auto-import
column.name.method.entry.point=Method

View File

@@ -597,7 +597,7 @@ settings.code.style.general.autodetect.indents=Detect and use existing file inde
import.scheme.chooser.source=From\:
import.scheme.chooser.destination=To\:
checkbox.reformat.on.typing.rbrace=Reformat block on typing '}'
settings.code.style.import.xml.error.invalid.file=The file doesn''t seem to be a valid Intellij IDEA XML scheme, it should contain ''code_scheme root'' element, found ''{0}'' instead.
settings.code.style.import.xml.error.invalid.file=The file doesn''t seem to be a valid IDE XML scheme, it should contain ''code_scheme root'' element, found ''{0}'' instead.
settings.code.style.import.xml.error.missing.scheme.name=Scheme 'name' attribute not found.
settings.code.style.import.xml.error.can.not.load=Can''t load code style scheme {0}.
@@ -678,12 +678,12 @@ settings.editor.scheme.import.chooser.title=Choose Schemes
settings.code.style.visual.guides=Visual guides
settings.code.style.visual.guides.optional=Optional
settings.code.style.general.visual.guides.hint=Specify one guide (80) or several (80, 120)
settings.export.target.intellij.xml=IntelliJ IDEA code style XML
settings.export.target.color.scheme=IntelliJ IDEA color scheme (.icls)
settings.export.target.intellij.xml=IDE code style XML
settings.export.target.color.scheme=IDE color scheme (.icls)
settings.export.target.color.scheme.plugin=Color scheme plugin .jar
settings.import.source.color.scheme=IntelliJ IDEA color scheme (.icls) or settings (.jar)
settings.export.inspection.profile.xml=IntelliJ IDEA inspection profile XML
settings.import.inspection.profile.xml=IntelliJ IDEA inspection profile XML
settings.import.source.color.scheme=IDE color scheme (.icls) or settings (.jar)
settings.export.inspection.profile.xml=IDE inspection profile XML
settings.import.inspection.profile.xml=IDE inspection profile XML
margin.columns=columns
combobox.lineseparator.for.new.files.hint=Applied to new files

View File

@@ -3045,8 +3045,8 @@ plugin.updater.not.installed.misc=Plugin update was not installed: {0}
plugin.updater.not.installed.see.log.action=See the log for more information
plugin.message.plugin.only.supported.in=This plugin is available only in {0}.
reportProblemAction.progress.title.submitting=Submitting\u2026
reportProblemAction.upload.logs.title=Send Logs to JetBrains?
reportProblemAction.upload.logs.message=By clicking \u201CYes\u201D you agree to send the logs of {0} to facilitate communication with JetBrains technical support. \
reportProblemAction.upload.logs.title=Send Logs?
reportProblemAction.upload.logs.message=By clicking \u201CYes\u201D you agree to send the logs of {0} to facilitate communication with technical support. \
Logs may contain private info such as system info and info about the projects opened in the IDE. \
If it is not possible to upload logs automatically, you can still send a separate, editable log as an attachment. \
If you do not send a log, we may be unable to help you with your issue.
@@ -3120,8 +3120,8 @@ title.language.and.region=Language and Region
combobox.language.option=Language
combobox.language=Language:
combobox.region=Region:
combobox.region.comment=Select a region to ensure that licensing, JetBrains Marketplace, and<br>other region-specific features and links work correctly. Requires<br>restart. See the <a href="{0}">documentation</a> for details.
combobox.region.hint=Select a region to ensure that<br>licensing, JetBrains Marketplace,<br>and other region-specific features<br>and links work correctly. Requires<br>restart.
combobox.region.comment=Select a region to ensure that licensing, marketplace, and other<br>region-specific features and links work correctly. Requires<br>restart. See the <a href="{0}">documentation</a> for details.
combobox.region.hint=Select a region to ensure that<br>licensing, marketplace, and<br>other region-specific features<br>and links work correctly. Requires<br>restart.
combobox.region.hint.link=Documentation
item.get.more.languages=Get More Languages\u2026

View File

@@ -1,5 +1,5 @@
title.language.and.region=Language and Region
description.language.and.region=<p align="center">Select a region to ensure that licensing, JetBrains Marketplace, and other region-specific features and links work correctly. See the <a style="display:none" href='https://www.jetbrains.com/help/idea/2024.2/language-and-region.html'>documentation</a> for details</p>
description.language.and.region=<p align="center">Select a region to ensure that licensing, marketplace, and other region-specific features and links work correctly. See the <a style="display:none" href='https://www.jetbrains.com/help/idea/2024.2/language-and-region.html'>documentation (TODO: change link to OpenIDE)</a> for details</p>
language.en=English
language.zhCN=Chinese (Simplified) \u4E2D\u6587\u8BED\u8A00\u5305

View File

@@ -456,7 +456,7 @@ action.FindPrevWordAtCaret.text=Previous Occurrence of the Word at Caret
action.FindPrevWordAtCaret.description=Find previous occurrence of the word at caret
action.ToggleFindInSelection.text=Search in Selection Only
action.IncrementalSearch.text=Incrementa_l Search
action.IncrementalSearch.description=Start incremental search (searches string as you type), IntelliJ IDEA 6.0 implementation.
action.IncrementalSearch.description=Start incremental search (searches string as you type).
action.FindUsages.text=Find _Usages
action.FindUsages.description=Find usages of the symbol at caret
action.ShowUsages.text=_Show Usages
@@ -1290,7 +1290,7 @@ action.Help.KeymapReference.text=_Keyboard Shortcuts PDF
action.Help.KeymapReference.description=Open PDF file with the default keymap reference card.
action.Help.JetBrainsTV.text=Product on YouTube
action.Help.JetBrainsTV.templateText={0} on YouTube
action.Help.JetBrainsTV.description=View short live demos introducing features of JetBrains products.
action.Help.JetBrainsTV.description=View short live demos introducing features of OpenIDE.
action.CheckForUpdate.text=_Check for Updates\u2026
action.CheckForUpdate.description=Checks for available IDE and plugin updates
action.CheckForUpdate.description.plugins=Checks for available plugin updates (IDE updates are managed externally)
@@ -1569,9 +1569,9 @@ action.EditCustomVmOptions.description=Opens an editor tab with a custom VM opti
action.LogDebugConfigure.text=D_ebug Log Settings\u2026
action.LogDebugConfigure.description=Enable or disable additional log categories. Allows to provide more information to the support team by request.
action.TechnicalSupport.text=Contact _Support\u2026
action.TechnicalSupport.description=Contact technical support on JetBrains website
action.TechnicalSupport.description=Contact technical support on OpenIDE website
action.ReportProblem.text=Submit a Bug Report\u2026
action.ReportProblem.description=Submit a bug report in JetBrains issue tracker
action.ReportProblem.description=Submit a bug report in OpenIDE issue tracker
action.TextComponent.ClearAction.text=Clear text
action.TextComponent.ClearAction.description=Clear text in text components

View File

@@ -5,7 +5,7 @@ filetype.idea.project.display.name=IDEA project
global.library.display.name=Global {0, choice, 1#Library|2#Libraries}
libraries.node.text.ide=Libraries contain classes that add up various functionality to your applications. \
Libraries also include source files and JavaDocs that can help you develop your projects.<br><br>\
IntelliJ IDEA uses libraries to assist you with code completion, validation, error highlighting, etc.<br><br>\
IDE uses libraries to assist you with code completion, validation, error highlighting, etc.<br><br>\
Global libraries are referenced through the entire project and can be used from all modules. \
Also they are available to all projects create locally on your computer.<br><br>\
Note that Global libraries are not available to anybody you share your project with. \
@@ -14,12 +14,12 @@ libraries.node.text.ide=Libraries contain classes that add up various functional
To attach a library to a module, select that module, click the Dependencies tab, click Add and specify the library location.
libraries.node.text.module=Libraries contain classes that add up various functionality to your applications. \
Libraries also include source files and JavaDocs that can help you develop your projects.<br><br>\
IntelliJ IDEA uses libraries to assist you with code completion, validation, error highlighting, etc.<br><br>\
IDE uses libraries to assist you with code completion, validation, error highlighting, etc.<br><br>\
Module libraries are referenced only from the module they are attached to. Expand the node and select child items to manage Module libraries.<br><br>\
To attach a library to a module, select that module, click the Dependencies tab, click Add and specify the library location.
libraries.node.text.project=Libraries contain classes that add up various functionality to your applications. \
Libraries also include source files and JavaDocs that can help you develop your projects.<br><br>\
IntelliJ IDEA uses libraries to assist you with code completion, validation, error highlighting, etc.<br><br>\
IDE uses libraries to assist you with code completion, validation, error highlighting, etc.<br><br>\
Project libraries are referenced through the entire project and can be used from all modules. \
Also they are available to everybody you share the project with.<br><br>Expand the node and select child items to manage Project libraries.<br><br>\
To attach a library to a module, select that module, click the Dependencies tab, click Add and specify the library location.

View File

@@ -1311,7 +1311,7 @@ ide.open.file.in.temp.project.dir=true
ide.open.file.in.temp.project.dir.description=Enables opening file in temp project directory
embed.scene.builder=true
embed.scene.builder.description=Show SceneBuilder embedded into IntelliJ IDEA frame
embed.scene.builder.description=Show SceneBuilder embedded into IDE frame
new.retina.detection=false
new.retina.detection.description=New implementation to detect retina devices

View File

@@ -407,7 +407,7 @@ testdata.related.navigation.title=Test data
# UpdateFromSources
action.UpdateIdeFromSourcesSettings.text=Update IDE from Sources Settings\u2026
action.UpdateIdeFromSources.text=Update IDE from Sources\u2026
action.UpdateIdeFromSources.description=Builds an installation of IntelliJ IDEA from the currently opened sources \
action.UpdateIdeFromSources.description=Builds an installation of IDE from the currently opened sources \
and updates the current (or another) installation with the result.
action.UpdateIdeFromSourcesAction.task.title=Updating from Sources
action.UpdateIdeFromSourcesAction.task.failed.title=Update from sources failed

View File

@@ -6,10 +6,10 @@
<![CDATA[
Enables interoperability with Eclipse and provides the following features:
<ul>
<li>Open Eclipse project in IntelliJ IDEA</li>
<li>Import Eclipse project into IntelliJ IDEA</li>
<li>Export IntelliJ IDEA project into Eclipse</li>
<li>Convert IntelliJ IDEA module to Eclipse-compatible format</li>
<li>Open Eclipse project in OpenIDE</li>
<li>Import Eclipse project into OpenIDE</li>
<li>Export OpenIDE project into Eclipse</li>
<li>Convert OpenIDE module to Eclipse-compatible format</li>
<li>Synchronize Eclipse project files</li>
</ul>
<p/>

View File

@@ -1,7 +1,7 @@
eclipse.name=Eclipse
eclipse.import.label.select.workspace=&Select Eclipse projects directory:
eclipse.import.title.select.workspace=Select Eclipse projects directory
eclipse.import.title.module.dir=Select directory for IntelliJ IDEA project and module files
eclipse.import.title.module.dir=Select directory for IDE project and module files
eclipse.import.warning.undefinded.libraries=Imported project refers to unknown global libraries
eclipse.import.converting=Converting Eclipse Projects
eclipse.import.scanning=Scanning Eclipse projects
@@ -15,12 +15,12 @@ filetype.eclipse.description=Eclipse project
filetype.eclipse.display.name=Eclipse Project
eclipse.create.library.title=Locate Eclipse Installation
eclipse.create.library.description=<html>Some of the projects you are importing depend on Eclipse platform.<br>\
IntelliJ IDEA will create a global library named {0} containing Eclipse libraries.</html>
IDE will create a global library named {0} containing Eclipse libraries.</html>
eclipse.import.code.style.default.option=Use default project code style
eclipse.import.code.style.import.option=Import code style from Eclipse project
eclipse.import.code.style.default.hint=Settings | Editor | Code Style
eclipse.import.code.style.import.hint=<html>One code style per project is supported. Not all Eclipse code style settings can be mapped to\
Intellij IDEA settings,<br>so the best possible approximation will be used.
IDE settings,<br>so the best possible approximation will be used.
eclipse.import.code.style.organize.imports.box=Import "Organize Imports" settings
list.empty.text.code.styles.not.found=Code styles not found
border.text.choose.project.code.style=Choose project code style
@@ -53,10 +53,10 @@ label.path.to.resulting.userlibraries=&Path to resulting .userlibraries
checkbox.export.non.module.libraries=E&xport non-module libraries
border.title.modules.to.export=Modules to export
checkbox.switch.selected.modules.to.eclipse.compatible.format=Convert selected modules into &Eclipse-compatible format
checkbox.link.created.intellij.idea.modules.to.eclipse.project.files=&Link created IntelliJ IDEA modules to Eclipse project files
checkbox.link.created.intellij.idea.modules.to.eclipse.project.files=&Link created IDE modules to Eclipse project files
radio.button.create.module.files.near.classpath.files=Create module files near .classpath files
label.detect.test.sources.comma.separated.path.masks.and.wildcards.allowed=Detect &test sources (comma-separated path masks, '*' and '?' wildcards allowed):
border.title.intellij.idea.project.and.module.files.location=IntelliJ IDEA project and module files location
border.title.intellij.idea.project.and.module.files.location=IDE project and module files location
radio.button.keep.project.and.module.files.in=Keep project and module files in
border.title.choose.project.code.style=Choose project code style
eclipse.color.theme.name=Eclipse color theme (XML)

View File

@@ -6,7 +6,7 @@
<vendor>JetBrains</vendor>
<description><![CDATA[
<p>Handles properties in <i>.editorconfig</i> files and applies them to all supported languages in all JetBrains IDEs.
<p>Handles properties in <i>.editorconfig</i> files and applies them to all supported languages.
<h2>Features</h2>
<ul>
@@ -14,7 +14,7 @@
</ul>
<h2>Getting started</h2>
<p>For more information,
check the documentation for <a href="https://editorconfig.org/">EditorConfig</a> files and your <a href="https://www.jetbrains.com/help/">IDE</a>.
check the documentation for <a href="https://editorconfig.org/">EditorConfig</a> files and your <a href="https://openide.ru/help/">IDE</a>.
]]></description>
<depends>com.intellij.modules.lang</depends>

View File

@@ -4,7 +4,7 @@ welcome.promo.start.tour.java=Start Tour in Java
welcome.promo.start.tour.kotlin=Start Tour in Kotlin
kotlin.onboarding.invoke.intention.for.warning.1=You have just fixed a bug, but you can make this code look even better. \
IntelliJ IDEA highlights and adds a yellow bulb to the code lines that can be improved.
IDE highlights and adds a yellow bulb to the code lines that can be improved.
kotlin.onboarding.invoke.intention.for.warning.2=Press {0} to preview the warnings and apply a quick-fix.
kotlin.onboarding.invoke.intention.for.warning.balloon=Press {0} to show available quick-fixes
kotlin.onboarding.select.fix=Apply the first item: {0}. In this case, the <strong>for-each</strong> loop will make code easier to understand.

View File

@@ -1,2 +1,2 @@
kotlin.coding.conventions.title=Kotlin Coding Conventions
kotlin.obsolete.coding.conventions.title=Kotlin obsolete IntelliJ IDEA codestyle
kotlin.obsolete.coding.conventions.title=Kotlin obsolete IDE codestyle

View File

@@ -23,6 +23,6 @@ build.process.info.kotlin.version=Kotlin version:
build.process.info.groovy.build.file.count=Number of Gradle Groovy build files:
build.process.info.kts.build.file.count=Number of Gradle Kts build files:
build.process.info.months.of.kotlin.usage=Months of Kotlin usage:
build.process.info.months.of.idea.usage=Months of IntelliJ IDEA usage:
build.process.info.months.of.idea.usage=Months of IDE usage:
action.org.jetbrains.kotlin.onboarding.gradle.ShowBuildProcessSatisfactionDialogAction.text=Show Kotlin Gradle Build Process Satisfaction Survey

View File

@@ -36,7 +36,7 @@ maven.settings.importing.use.output.directories=Use Maven &output directories
maven.settings.importing.use.output.directories.tooltip=IDEA compiler will use output directory defined in maven model (target/classes by default)
maven.settings.importing.generated.source.folders=Generated sources folders:
maven.settings.importing.phase.for.source.updates=Phase to be used for folders &update:
maven.settings.importing.phase.for.source.updates.notes=<html>IntelliJ IDEA needs to execute one of the listed phases in order to \
maven.settings.importing.phase.for.source.updates.notes=<html>IDE needs to execute one of the listed phases in order to \
discover all source folders that are configured via Maven plugins.\
<br><b>Note</b> that all test-* phases firstly generate and compile production sources.</html>

View File

@@ -86,7 +86,7 @@ progress.title.starting.maven.server=Starting Maven server
maven.sync.not.trusted.title=Untrusted project
#leave link html markup - i.e. <a href="{0}">Translation goes here</a>
maven.sync.not.trusted.description=The opened untrusted project is not fully loaded. \n\
IntelliJ IDEA will not resolve any plugins in the project, download artifacts, or execute any goals
IDE will not resolve any plugins in the project, download artifacts, or execute any goals
maven.sync.trust.project=Trust project
maven.sync.wsl.maven.is.not.wsl=Maven distribution looks incorrect
maven.sync.wsl.maven.is.not.wsl.description=Maven home resolved to {0}.\n For performance reason better to use maven installed in wsl distribution. <a href="{1}">Open settings</a>

View File

@@ -398,7 +398,7 @@ delete.component.title=Delete Component
insert.feedback.fill=fill
insert.feedback.add.tab=Add tab: {0} ({1})
generate.main.title=Generate main()
generate.main.not.valid.form=The form bound to the class is not a valid IntelliJ IDEA form
generate.main.not.valid.form=The form bound to the class is not a valid IDE form
generate.main.no.default.constructor=The class does not have a default constructor
generate.main.empty.form=The form bound to the class is empty
generate.main.no.root.binding=The form bound to the class does not have a valid binding for the root component

View File

@@ -12594,15 +12594,15 @@
<option name="history" path="ActionManager" hit="View history of committed changes" />
<option name="of" path="ActionManager" hit="View history of committed changes" />
<option name="view" path="ActionManager" hit="View history of committed changes" />
<option name="demos" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="features" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="introducing" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="jetbrains" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="live" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="of" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="products" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="short" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="view" path="ActionManager" hit="View short live demos introducing features of JetBrains products." />
<option name="demos" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="features" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="introducing" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="jetbrains" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="live" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="of" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="products" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="short" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="view" path="ActionManager" hit="View short live demos introducing features of OpenIDE." />
<option name="a" path="ActionManager" hit="View text value of selected node in a separate pane" />
<option name="in" path="ActionManager" hit="View text value of selected node in a separate pane" />
<option name="node" path="ActionManager" hit="View text value of selected node in a separate pane" />
@@ -33592,39 +33592,39 @@
</configurable>
<configurable id="reference.settings.project.maven.importing" configurable_name="Importing">
<option name="" hit="" />
<option name="" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="all" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="and" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="are" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="b" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="br" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="compile" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="configured" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="discover" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="execute" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="firstly" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="folders" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="generate" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="html" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="idea" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="in" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="listed" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="maven" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="needs" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="note" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="of" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="one" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="order" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="phases" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="plugins" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="production" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="source" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="sources" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="test-" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="that" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="the" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="to" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="via" hit=" IDEA needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="all" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="and" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="are" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="b" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="br" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="compile" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="configured" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="discover" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="execute" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="firstly" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="folders" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="generate" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="html" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="idea" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="in" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="listed" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="maven" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="needs" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="note" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="of" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="one" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="order" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="phases" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="plugins" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="production" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="source" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="sources" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="test-" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="that" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="the" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="to" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="via" hit=" IDE needs to execute one of the listed phases in order to discover all source folders that are configured via Maven plugins. Note that all test-* phases firstly generate and compile production sources. " />
<option name="automatically" hit="Automatically download:" />
<option name="download" hit="Automatically download:" />
<option name="be" hit="Comma separated list of dependency types that should be imported" />