Opened 8 years ago
Closed 6 years ago
#44662 closed enhancement (fixed)
Text length of the Incremental search of link in tinymce should be localizable
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 5.4 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | I18N | Keywords: | has-patch |
| Focuses: | Cc: |
Description
related: #44541
Incremental search of link in tinymce should fire from 2 chars in Japanese. These fixes are included in the WP Multibyte Patch plugin in the Japanese package.
So, the number should be localizable.
Attachments (5)
Change History (20)
#2
@
8 years ago
Following is a list of tickets to improve multibyte enhancement.
https://docs.google.com/spreadsheets/d/13oGbc7AqEN6OUvmze-JDCKXDdruFqsxqSAdI7-b6Lho/edit#gid=0
#3
@
8 years ago
IMHO this also needs a context that's better to understand than search internal links. Something like minimum search input word length or so.
#4
@
8 years ago
Hi @swissspidy
Thanks for your review.
i fixed to make it easier to understand that search starts from the 3rd character.
https://core.trac.wordpress.org/attachment/ticket/44662/44662.3.patch
#5
@
8 years ago
- Keywords needs-refresh added
- Milestone changed from Awaiting Review to 5.0
Thanks for the patch! A few suggestions:
- Let's try to reduce the context to 5-6 words
- Cast the value to an integer (
(int) _x( … )) - Provide a fallback if
(int) _x( … )returns 0
#6
@
8 years ago
@ocean90 Thank you Review!
add new patch. https://core.trac.wordpress.org/attachment/ticket/44662/44662.4.patch
add fallback for _x( … ) return 0 or not number value.
#7
@
8 years ago
- Milestone changed from 5.0 to 5.1
Moving to the 5.1 milestone due to the WordPress 5.0 focus on the new
editor (Gutenberg).
#9
@
7 years ago
- Milestone changed from 5.2 to 5.3
This has not seen any action during the 5.2 cycle. Punting to 5.3 since 5.2 beta 1 is fast approaching.
#10
@
7 years ago
- Keywords needs-refresh removed
The patch 44662-5.diff is a minor refresh that
1) Replaces the typo serchLength with searchLength.
2) Fixes the PHPCS issue:
1395 | ERROR | [x] Expected 1 space after closing brace; newline found
3) Replaces the for part in variables:
$minimum_word_length_for_search minimumWordLengthForSearch
with:
$minimum_search_word_length minimumSearchWordLength
4) Combines the variable defining parts of patch 44662.4.patch
I tested this by increasing the minimum search word length to 5 (instead of 3) in the patch and that seems to work as expected on my test install.
This is a one of a series of patches to fix problems for Japanese package.
Related: #meta3163, #43829, #44296, #44541, #15955, #22363, #44548