_s日本語ファイル更新 #2
Open
_s日本語ファイル更新 #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update the replace example in README.md
* upstream/master: (57 commits) Fix the issue with naming after merge Bumping the long overdue (Tested up to:) version number. Use the_header_image_tag() function. Add word-wrap: normal to screen-reader text class. Fix skip link focus. Remove aria-haspopup. Remove link around header image. Add missing " after automattic.com. What am I doing here:) Add rel="designer" back in for master branch. Remove rel="designer" from footer. Add theme support for selective refresh for widgets. Update style.css Fix typo and update link _s_pingback_header should use get_bloginfo instead of bloginfo because echo is already being used to output the link tag (entire line) Remove period from file header Remove period from file header Remove period from file header Remove period from file header Remove period from file header Remove period from file header ... # Conflicts: # languages/_s.pot
…use of screen reader text
Adding word-wrap to .screen-reader-text to improve accessibility just like in style.css
Matching Style.css
Change 1.5em to 100% to prevent magic numbers.
Remove post-formats from tags
Clarify who maintains _s
Fix translatability of comments title
…ation Code obfuscation: Fix assignment within a condition
…n-call-context I18n: Fix a translation call for a text string which needs context
…ayout I18n and code layout improvements. * Fixes missing /* translators */ comments for translatable text strings containing placeholders. * Fixes infractions against the "For associative arrays, values should start on a new line." code style rule.
* Switches to 2.9 branch to avoid failed builds for now. See: Automattic#1067 (comment) See Automattic#1079
Everything which is defined in the global namespace should be prefixed to prevent conflicts with other themes and plugins. This snippet enables the sniff which verifies this and tells it which prefix to look for.
WordPress provides backfills for a number of PHP native functions and constants. These can therefore be safely used in themes and plugins. This commit adds a whitelist for the PHPCompatibility ruleset of the backfills currently provided by WP. N.B.: At this moment, none of the whitelisted classes/constants/functions/interfaces are used in `_s`. However, `_s` is also a teaching tool and an example for others, so having this whitelist block in there serves that purpose and allows for themes which are build onto `_s` to use these PHP features without having to worry about cross-version compatibility notices.
The ruleset contained some exclusions which are no longer needed.
The one in `functions.php` can be considered a bug in WPCS and has been reported as such. Once that issue is fixed, the whitelisting can be removed. The one in `inc/wpcom.php` will need to remain as WPCS does not keep track of globals introduced by wpcom.
This fixes a few of the errors from the news sniffs in WPCS 0.12.0 and also standardizes the indention between the PHP and HTML
While template files are intended to be included from within a function, this doesn't guarantee they always will be. Therefore all variables declared within template files also need to be prefixed with a theme specific prefix. As these are "local" variables, renaming them does not constitute a BC-break.
This line was quite unreadable. Additionally, it was using the "heavy" `wp_kses_data()` function to escape item count phrase, while that phrase should not contain HTML in the first place and therefore can use the lighter `esc_html()` function to do the output escaping.
…e the post format removal that was started in Automattic#1017. Fixes Automattic#1148.
Update Normalize.css to v8.0.0
…post-format-function-call Replace the get_post_format() calls in get_template_part() with get_post_type()
Two travis tweaks - speed up build times by disabling Xdebug - stop build testing against HHVM, test against nightly
Clarify "singularly identifiable articles"
Bring code style up to the latest standards - This PR addresses code-style issues identified when testing the code against the WordPress Coding Standards.
Fix datetime values
no-sidebar class
Add details to documentation about the enabled features and how the intergration is linked to theme
Replace http with https in header.php
…o-featured-images Add 'tabindex=-1' to the featured image markup, to improve accessibil…
Discussed in Automattic#1268 This PR removes .hentry microformat class, adds `.post` and `.page` instead ( in both `_posts-and-pages.scss` & `style.css` ).
Is it OK?
Unscramble echo to readable printf
Add WooCommerce to docs
Remove Microformat Classes `.hentry`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
最新版（Version: 1.3-wpcom）に合わせた日本語翻訳ファイルとその他のコミットです